feat: send key-annotated event fields as TargetParameters for direct record navigation#50
Open
busehalis-sap wants to merge 2 commits into
Open
feat: send key-annotated event fields as TargetParameters for direct record navigation#50busehalis-sap wants to merge 2 commits into
busehalis-sap wants to merge 2 commits into
Conversation
…record navigation
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.
Summary
The Node.js notifications plugin already supported navigation target parameters: Event fields marked with the
keykeyword are sent as TargetParameters to ANS. This PR brings the same feature to the CAP Java plugin.Changes
key-annotated fields are extracted asTargetParameters, non-key fields remain as Propertieskey-annotated fields are excluded from the notification templatePropertiesSchema, since they are navigation parameters and not template placeholders