Strip generated content #440
Merged
Conversation
This file contains 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.
*Add new operation stripGeneratedContent
For Knowledge Artifacts (Measures, Libraries, PlanDefinition, Questionnaires) test data we can strip anything that can be generated or inferred at runtime. Specifically: text, data-requirements, parameters, related-artifacts (of type "depends-on"), content of type application/elm+json or application/elm+xml
Basically, the opposite of RefreshIG and RefreshLibrary.
The goal here is to make the test resources as easy to work with as possible. Removing any data that's not related to the functional behavior
By creating this PR you acknowledge that your contribution will be licensed under Apache 2.0