More metadata #268
Merged
More metadata #268
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
|
Does this solve #260 ? |
|
Yes, I think this solves #260. |
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.
Change metadata filtering, so that we can specify both "include" and "exclude" sets. This means that the
selectparameter should be a dictionary containing the keysincludeand/orexclude, both of which should be lists of attribute names. If one of these is specified as a an empty list, it is treated as missing.It is also possible to specify
selectas a list; this will be treated the same as a dictionary with the list as the value of the "include" key.The default value for
caseobjects is to include everything, while forchildobjects, we excludedata.spec.columnsandfmu.realization.parameters.