Repository navigation
[uss_qualifier/reports] Improve action generator descriptions - #1818
Merged
mickmis merged 1 commit intoOct 19, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Most (all?) action generators will be replaced with ResourceEnvironmentsActionGenerators because doing so provides the flexibility of a native for-loop rather than trying to define a special-purpose for-loop for each iterator variable type. This is generally a good thing that will make suite definitions simpler and more reusable, but the description shown in the sequence view index for these iterators is currently very unhelpful: "For each resource environment". It is true that it is iterating over resource environments, but that gives the reader virtually no information about the nature of the environments being iterated over. This PR addresses that issue by recording resource pool information at runtime (the time when it's available), and then using that information in the sequence view generator to be more helpful about what is being iterated over; e.g. "For each resource environment supplying uss1, uss2, and flight_intents".