port over potential optimizations to JsonDecoder
Open
Nobody has claimed this yet.
enhancement
helper
- Dominant language
- Java
- Stars
- 87
- Forks
- 73
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 1
Description
- in.getCurrentToken().isNumeric() vs in.getCurrentToken() == JsonToken.VALUE_NUMBER_INT
- disableFeature(JsonParser.Feature.INTERN_FIELD_NAMES) on JsonParser instances
Contributor 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.
Research direction
Start at the JsonDecoder implementation and trace the getCurrentToken() numeric check and JsonParser instance construction mentioned in the issue. Compare the existing behavior around these two potential optimizations, then run the repository's relevant tests to confirm decoding behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100