popcodeorg / popcodeorg/popcode
Use sourcemaps for runtime error line numbers
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 191
- Forks
- 143
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 5
Description
Right now our logic for finding out what line of the student’s JavaScript generated a runtime error is fragile, woolly, and different for different browsers.
Maybe we can hook into the source maps mechanism and provide a sourceUrl that is a data URI, which would then cause the browser to give us the right information?
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
Start by tracing the current logic that determines runtime-error line numbers, then investigate how browser source maps and a data-URI sourceUrl behave for generated student JavaScript. Done means reporting the correct source line consistently across supported browsers; the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100