GraphComparator: JSON path in fieldName
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by locating GraphComparator and reading how fieldName values are generated for nested JSON-like structures. Trace the existing comparison output and determine how a full path could distinguish identical leaf names; done means the displayed fieldName identifies each branch without breaking current comparisons.
Written by the indexing model from the issue text.
Description
Option to use whole JSON path in the fieldName in GraphComparator.
This would be greatly appreciated, because when having the same field names as leafs in different document branches, it's not obvious which one is shown.
- Dominant language
- Java
- Stars
- 442
- Forks
- 115
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 jdereg/java-util
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
All issues in jdereg/java-util
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100