How to do stream parsing?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading the AsyncParser API and the absorb entry point, using the Play JSON AST example in the issue as the expected integration. Determine whether parsing can expose individual elements incrementally rather than one jsobject, and check the existing parser tests for streaming behavior. Done means the supported approach is documented or the requested incremental output is implemented and covered by tests.
Written by the indexing model from the issue text.
Description
I have tried to use the AsyncParser but I couldn't figure out how to get anything out other than a single jsobject as defined by my AST (in this case Play JSON).
Assume I have something like:
{
"name": "thing"
"elements": [{
"key": "a",
"value": "alice"
},{
"key": "b",
"value": "bob"
},
...
]
}
How can I get it so that each call to absorb will return zero or more elements?
- Dominant language
- Scala
- Stars
- 436
- Forks
- 72
- Avg merge
- 29m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from typelevel/jawn
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Allowing commentsOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
requires-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/datafusion-comet#7001 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lichess-org/lila#22088 ·
Maintainers usually reply within 1 day
-
agent-ready area/dev-tooling layer/infra size/S
Difficulty 1/5 Under an hour Newbie friendliness 90/100
marola-dev/marola-app#111 ·
Maintainers usually reply within 1 day
-
agent-ready area/dev-tooling kind/docs-only layer/docs size/XS
Difficulty 2/5 Under an hour Newbie friendliness 72/100
marola-dev/marola#824 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day