Post

Babak Farhang
@gnahraf.bsky.social

Wow. Also jealous. Re the json api and building (writing) the json structure.. I was wondering the same in a convo here with the contributor bsky.app/profile/did:... I use a knock off of github.com/fangyidong/j... w/ small fixes and customizations. I Iike immutable objects on the read-path 1/

github.comGitHub - fangyidong/json-simple: A simple Java toolkit for JSON. You can use json-simple to encode or decode JSON text.A simple Java toolkit for JSON. You can use json-simple to encode or decode JSON text. - fangyidong/json-simple
Naoto Sato@naotoj.bsky.social

github.com/openjdk/jdk/...

github.com8381976: Implement JEP 540: Simple JSON API (Incubator) by naotoj · Pull Request #32282 · openjdk/jdkThis PR implements JEP 540: Simple JSON API (Incubator). It adds the jdk.incubator.json module which provides APIs for reading and writing JSON documents as specified by RFC 8259. This is an incuba...
Babak Farhang
@gnahraf.bsky.social

but I think it the write-path will need mutable abstractions (JsonObjectBuilder or perhaps a MutableJsonObject). This first incubator release only considers the read-path; the write-path is to be punted to a future (incubation) release. I'll join the mailing list.. better to contrib ideas early. 2/2

Cay Horstmann
@horstmann.com

I don't think that writing requires mutable JSON structures, but I am hoping for an API to express common transformations. It would not be good if every API user wishing to transform JSON had to reimplement a tree copy.

0 reposts0 likes

Babak Farhang
@gnahraf.bsky.social

Agree, I wouldn't want that either (tree copy just to mutate). I was thinking more like each mutator method returning a new immutable instance, good copy-on-write strategies, etc..