Simplify Building PathExtractors without Annotations #33
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
tgregg
approved these changes
Jan 8, 2025
rmarrowstone
force-pushed
the
search-api
branch
from
cf45a2c to
3180ae2
Compare
This change makes it simpler to programmatically register search paths which don't have annotations. Without this change, users need to provide empty annotations for both the TLV matching and each path step.
rmarrowstone
force-pushed
the
search-api
branch
from
3180ae2 to
8d467ac
Compare
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 change makes it simpler to programmatically register search
paths which don't have annotations. Without this change, users need
to provide empty annotations for both the TLV matching and each
path step.