Unable to provide URL in custom JSON fields
See original GitHub issueSteps to reproduce the problem:
- Create new gist with below as metadata:
{
"name": {
"title": "Full Name",
"type": "string",
"githubKey": "name"
},
"privacy": {
"title": "I acknowledge the Privacy Policy - https:\/\/website.com\/legal\/privacy-policy",
"type": "boolean",
"required": true
}
}
- Configure a new link with above gist as CLA.
- Try to sign it.
What is the expected result? That it parses the privacy.title field as valid json. the culprit is the colon as using: https//website.com/legal/privacy-policy as the title will make the gist parse successfully.
What happens instead?
(Unexpected token h in JSON at position 671)
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Custom Connector unable to process json correctly
Hello, I'm trying to create an action for an api for my custom connector and when I import from sample for the request...
Read more >CLA Stopped working, error: Unexpected token in JSON · Issue ...
KharitonOff mentioned this issue on Feb 15, 2021. Unable to provide URL in custom JSON fields #660. Open. @snyk-bot snyk-bot mentioned this issue...
Read more >Not able to convert Json with @ in field to custom java Object
This is because you are not use Jackson's ObjectMapper to output the BookInfo as a JSON string. In the first attempt, you are...
Read more >Advanced field editing using JSON | Cloud automation Cloud
The More options field on automation actions in Jira Cloud allow you to specify a valid JSON object reference and edit issue fields....
Read more >Error while parsing JSON Response in REST API Post call
I was able to resolve the issue. I had forgotten to append "?format=json" at the end of the REST url. So it was...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I tried debugging this myself yesterday evening, but this is essentially the first time I working with Angular/Javascript - I hope to continue the debugging the next couple of evening… If I find a fix I intent to make a PR.
Any pointers or help in regards to this would be greatly appreciated.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.