Update access-header-and-properties-in-xpath-996ce78.md #84
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
java.lang.Number is the correct Data Type for MaxPrice as it is in integer
|
|
|
Hi @vaibhavhupadhyay, thanks for your contribution, but it looks like you still haven't signed the contributor license agreement. Please accept the agreement so we can accept your contribution. Thanks! |
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.
java.lang.Number is the correct Data Type for MaxPrice as it is in integer. And the earlier data type mentioned java.lang.String will be not work in Message Filter where the property MaxPrice is invoked for filtering the reply received from ESPM.