Add ability to get status overview of child records #792
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This adds the ability to get the status counts of 'child' records (for example, optimizations as part of a torsiondrive or gridoptimization service). See Issue #791
It should be noted that most services generate records as needed, so the status that is returned is not indicative of progress (ie, if there is only one record remaining to be run, it is not guaranteed that that is the last remaining calculation to be run - others may be generated after that is completed).
Status can be obtained with the
record.children_status
property. This is available on all record types, although Singlepoint records will always return an empty dictionary.Changelog description
Add ability to get status overview of child records
Status