Merged
Conversation
A "trait" relationship allows selectors to traverse from shapes to the the trait shapes applied to the shape. This can be used to query for things like "services with no protocol traits", "deprecated traits that are being used on shapes", "traits that aren't referenced by any shapes", etc. Trait relationships are not typically needed and add a lot of overhead. As such, they are opt-in only and enabled in selectors by adding a named "trait" directed relationship. They're also opt-in in code. In order to pull this off, I updated the selector API to always require a Model.
mtdowling
force-pushed
the
add-trait-relationship
branch
from
4da0f12 to
1d496c5
Compare
kstich
approved these changes
Apr 17, 2020
Merged
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.
A "trait" relationship allows selectors to traverse from shapes to the
the trait shapes applied to the shape. This can be used to query for
things like "services with no protocol traits", "deprecated traits that
are being used on shapes", "traits that aren't referenced by any
shapes", etc.
Trait relationships are not typically needed and add a lot of overhead.
As such, they are opt-in only and enabled in selectors by adding a named
"trait" directed relationship. They're also opt-in in code.
In order to pull this off, I updated the selector API to always require
a Model.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.