Is it necessary to do strong check on fastjson?
Open
kind/discussion
kind/enhancement
- Dominant language
- Java
- Stars
- 23.1k
- Forks
- 8.1k
- PR merge metrics
- No merged PRs in 30d
Description
## Issue Description
Rules' deserialization will be interrupted with old version of fastjson due to the bug on inherited bean classes.
Should we add some kinds of force check on it?
Contributor guide
Research direction
No source file, test, or entry point is named. Start by reviewing the unresolved comment thread and reproducing Rules deserialization with an old fastjson version and inherited bean classes; done should mean an agreed compatibility check and a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100