NativeScript / NativeScript/android
JSParser error should point to original file of the error not bundle.js
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 563
- Forks
- 144
- Avg merge
- 10h 46m
- Merged PRs (30d)
- 14
Description
- JSParser error should point to original file of the error not bundle.js
- The line of the error should be added too
JSParser Error: Not enough or too many arguments passed(0) when trying to extend interface: java.util.List in file: bundle.js
Same logic has been implemented in cli for runtime errors.
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 by comparing JSParser error handling with the existing CLI runtime-error logic mentioned in the issue. Confirm how the parser currently reports bundle.js, then make the completed behavior identify the original source file and include the error line.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, javascript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100