Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Array nodes must support parameters, which implies a strict dependence on JSON.jl. #8

Closed
Tracked by #5
jpivarski opened this issue Aug 9, 2023 · 3 comments · Fixed by #9
Closed
Tracked by #5

Comments

@jpivarski
Copy link
Member

No description provided.

@Moelf
Copy link
Member

Moelf commented Aug 9, 2023

JSON3.jl is better

@jpivarski jpivarski linked a pull request Aug 9, 2023 that will close this issue
@jpivarski
Copy link
Member Author

As it turns out, I don't need a JSON library yet. But when I do, what I'll need most will be to iterate over the JSON, making decisions based on what types and values we encounter in the JSON. This iteration does not need to be fast; the JSON documents are never large. (I'm thinking about parameters, which are rarely anything more than a single string, and Forms, which are only type descriptions.)

Should I still be looking at JSON3.jl for that? It looks like it has something to generate concrete types, but for my purposes, the easiest thing would be for a library to give me Dict{String,Any} and Vector{Any}.

@Moelf
Copy link
Member

Moelf commented Aug 10, 2023

I guess both are well maintained, JSON3.jl's author also maintains CSV.jl, HTTP.jl, and Arrow.jl

JSON.jl is maintained by a bunch of involved Julia people as well, the package itself is older (started way before 1.0), while JSON3.jl is newer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants