KhronosGroup / KhronosGroup/glTF-Validator
Improve reporting of invalid UTF-8 encoding
Open
enhancement
- Dominant language
- Dart
- Stars
- 470
- Forks
- 77
- PR merge metrics
- No merged PRs in 30d
Description
- Add a new error code, do not use `INVALID_JSON` for this case.
- Ensure correct byte offsets in the report.
Motivated by #226.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the context in issue #226 and locating the validator's UTF-8 error handling and existing INVALID_JSON reporting. Check how byte offsets are calculated and reported. Done means invalid UTF-8 uses a distinct error code and the report contains correct byte offsets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100