You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Input Format: JSONL (JSON Lines)
Output Language: any
Description
Hello, I have used this project often for usual JSON files and it worked great. At work I have a project where large .jsonl files are used/generated. These are just files where every line is its own JSON object.
Current Behaviour / Output
Currently, there is no support for JSONL files.
Proposed Behaviour / Output
It would be amazing if there was an option for reading JSONL files.
Solution
Basically it should iterate through every line and build the types from there, kind of like the Multiple JSON features but just line by line instead of file by file. If I get around to it, I might add this myself and open a pull request.
Alternatives
I do not know of any alternatives currently.
Context
The files that are getting generated is basically a long list of symbols in a running system. Every line (JSON object) has a JSON property/field describing the kind of object it is. This is not a necessary requirement for parsing, just used afterwards when parsing the file for other purposes.
The text was updated successfully, but these errors were encountered:
Context (Input, Language)
Input Format: JSONL (JSON Lines)
Output Language: any
Description
Hello, I have used this project often for usual JSON files and it worked great. At work I have a project where large
.jsonl
files are used/generated. These are just files where every line is its own JSON object.Current Behaviour / Output
Currently, there is no support for JSONL files.
Proposed Behaviour / Output
It would be amazing if there was an option for reading JSONL files.
Solution
Basically it should iterate through every line and build the types from there, kind of like the Multiple JSON features but just line by line instead of file by file. If I get around to it, I might add this myself and open a pull request.
Alternatives
I do not know of any alternatives currently.
Context
The files that are getting generated is basically a long list of symbols in a running system. Every line (JSON object) has a JSON property/field describing the kind of object it is. This is not a necessary requirement for parsing, just used afterwards when parsing the file for other purposes.
The text was updated successfully, but these errors were encountered: