max-mapper / max-mapper/jsonpify
invalid JSONP/JS served when valid JSON has strange character in string
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 15
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This is a valid json file:
https://rawgit.com/Daniel-Hug/76ba7d9079d88fd7e635/raw/92ad99ff94d970619dd57babb8b3dcb8373a4148/badchar.json
This javascript file throws an error, though:
https://jsonpify.herokuapp.com/?resource=https://rawgit.com/Daniel-Hug/76ba7d9079d88fd7e635/raw/92ad99ff94d970619dd57babb8b3dcb8373a4148/badchar.json&callback=fooers
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 fetching the linked badchar.json resource through the jsonpify Heroku URL and inspect the generated response around the unusual character. Trace the JSON-to-JSONP handling from the repository entry point, then verify that the response is valid JavaScript and can be evaluated with the fooers callback without an error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100