linkedin / linkedin/linkedin-calcite
Unshaded json-path conflicting with newer versions in downstream dependencies
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 23
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Some consumers of coral have reported conflicts with newer versions of json-path. Since json-path is not exposes in the calcite API, it can be safely shaded.
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.
Research direction
No files or tests are named. Start by locating the project dependency and packaging configuration for json-path, then inspect how dependencies are exposed to consumers. Done means json-path is shaded so downstream users no longer encounter conflicts with newer versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100