Add ignore mechanisms for discovery via env, package.xml, and XML marker#97
Merged
Merged
Conversation
…cache invalidation
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
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.
This adds three opt-out mechanisms for discovery.
Packages can now be ignored through the
YASMIN_DISCOVERY_IGNORE_PACKAGESenvironment variable, through a flag inpackage.xml, or per state machine XML file with a special ignore comment on the first non-empty line.The env-based ignore list is also included in the cache state so discovery results are invalidated correctly when the ignore list changes.
I added the ignore tag to
yasmin_factoryso that the test state machines are ignored.