JsonPath setting by path and JSON facade #1
Closed
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
|
Hi, As you say it's a big change and it will break the projects where I use JsonPath today. I will definitely pick parts of your code when I find the time. Thank you for your input (and effort), it's appreciated! Best regards On Jul 29, 2011, at 11:24 PM, davefb wrote:
|
|
|
||
| </dependencies> | ||
| </project> | ||
| <?xml version="1.0"?> |
There was a problem hiding this comment.
I am not totally sure what we are doing here with these mass removals and additions. They look like copy paste.
|
This is to old now. |
KumarJayanti
referenced
this pull request
in KumarJayanti/JsonPath
Mar 15, 2019
… Configuration Option CREATE_MISSING_PROPERTIES_ON_DEFINITE_PATH needs to be set to enable this feature. Without this Option a Jsonpath.set() on a non-existent path would throw com.jayway.jsonpath.PathNotFoundException. 2. JSON -TO- JSON transformation : A new API and SPI (TransformationProvider) has been introduced to support JSON to JSON transformation specified using Source and Target JsonPath's. This feature makes use of #1 above to create/add the required attributes to the transformed target JSON. 3. As is the norm in JsonPath Framework, there can be several implementations of the TransformationProvider. This commit defines a particular Provider with its own JsonPath based TransformationSpec. The Spec allows for WildCard mappings (currently Single-Level) for array paths. It provides a notion of LookupTables that support custom mapping of a string/enumeration value in the source document to a value in the corresponding transformed target document. 4. Changes made to Configuration and Option classes to introduce this new Optional TransformationProvider API. 5. DefaultsImpl updated to provide a default instance of the transformationProvider implementation. 6. Changes to internal classes PathRef, PathToken and PropertyPathToken mainly to support #1 above. 7. New API added to AbstractJsonProvider, addArrayIndex to support #1 above. 8. New Files and Classes : API and SPI classes for TransformationProvider and TransformationSpec. 9. As an API the TransformationSpec provides the ability to get the spec as an opaque object and also one could validate the spec object. 10. Each implementation of the TransformationProvider can have its own TransformationSpec definition.
kallestenflo
pushed a commit
that referenced
this pull request
Apr 24, 2019
Update from json-path/JsonPath
PavelSakharchuk
referenced
this pull request
in PavelSakharchuk/contribut_JsonPath
Sep 22, 2023
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.
I did some feature enhancements to jsonpath as part of a project I'm working on. it's a pretty large change so you might not want to accept it wholesale, but feel free to take a look and use anything that might be useful to you. There are notes in the README.