Repository navigation
Getters for JsonPatch* class attributes #33
Description
Was there a particular design reason no getters were provided in the JsonPatch classes? I'm deserializing json over the wire into instances of these classes and attempting to provide for a JSR303 validation implementation allowing me to limit patch operations, without public methods to access class attributes (i.e. path), it's seemingly impossible. I'd hate to convert to something that I can access the attributes, it seems cumbersome.
Thoughts?
Activity
huggsboson commentedon Aug 4, 2015
I can't speak to @fge's rationale for it. fge hasn't really been responding here. I'm not sure if there is a new maintainer. If you made a pull request, I could find some time to setup a build on crate-metadata/json-patch and publish a build of it to maven central.
chb0github commentedon Jun 21, 2016
Time for a fork?
huggsboson commentedon Jun 21, 2016
I got the builds setup and am happy to accept pull requests at the crate-metadata/json-patch fork and build them to maven central @ net.box.json-patch. I'm in communication with @fge about getting access to his maven central repo so that I can push builds there but haven't heard anything yet.
chb0github commentedon Jun 29, 2016
Can you do an actual build and release so I can depend on it?
chb0github commentedon Jun 29, 2016
Can you do an actual build and release so I can depend on it?
huggsboson commentedon Jun 29, 2016
yeah I can do one at net.box#json-patch instead of com.github.fge#json-patch. We have to get the change merged over at the fork first though.
daveclayton commentedon Jul 7, 2016
HI @chb0github @huggsboson , is this still required?
Happy to consider creating a branch here for that - it sounds logical.
chb0github commentedon Jul 10, 2016
@daveclayton Well, anymore discussion about a a new release should be done on the forked repo as an issue and not here.
jvitrifork commentedon Jun 17, 2019
did anything happen to this feature request?
chb0github commentedon Jun 17, 2019