Creating team with '&' in name fails with "Bad signature: non-canonical JSON found in strict mode..."
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Version 1.0.33-20171003193446+d9ceb86ac on macOS 10.12.6
To reproduce:
-
Try to create team with a
&character in the name, likeA&B. -
I see a large error dump (white text on red box) at top of view starting with
Bad signature: non-canonical JSON found in strict mode....I'm assuming that any sensitive data is filtered out of that dump but just to be safe I'm not going to post a screen shot.
Just letting y'all know. Creating a team without & in the name seems to work fine, and that's what I did.
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
No file, test, or entry point is identified. Start by reproducing team creation with the name A&B on macOS and trace the resulting canonical-JSON error; done means the team is created successfully without the error dump.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100