In the API Docs on the wiki, for example here: https://go-wiki.ifrc.org/en/go-api/Connecting_to_GO_API#:~:text=Then%20enter%20%7B%22username%22%3A%20%E2%80%9Cyour%2Dusername%E2%80%9D%2C%20%22password%22%3A%20%E2%80%9Cyour%2Dpassword%E2%80%9D%7D.%20In%20the%20field%20%E2%80%9Cyour%2Dusername%E2%80%9D
The docs have in the example:
{"username": “your-username”, "password": “your-password”}
The quote characters there around your-username and your-password are not standard ASCII quote characters and will give errors if someone copy / pastes the example and edits it. (i.e. they have “ instead of "). We should fix all quote characters in the wiki docs to be standard ASCII so they are pasteable and don't cause hard-to-track-down errors for people trying to copy-paste examples.
This is a bit silly, and easy mistake to make when copy-pasting things around - the biggest culprit for me is always MS Word that insists on converting standard " characters to fancy “ characters.
This was a great catch by @wrynearson .
Don't think there's any urgency, but would be good to fix at some point.
cc @tovari @szabozoltan69
In the API Docs on the wiki, for example here: https://go-wiki.ifrc.org/en/go-api/Connecting_to_GO_API#:~:text=Then%20enter%20%7B%22username%22%3A%20%E2%80%9Cyour%2Dusername%E2%80%9D%2C%20%22password%22%3A%20%E2%80%9Cyour%2Dpassword%E2%80%9D%7D.%20In%20the%20field%20%E2%80%9Cyour%2Dusername%E2%80%9D
The docs have in the example:
The quote characters there around
your-usernameandyour-passwordare not standard ASCII quote characters and will give errors if someone copy / pastes the example and edits it. (i.e. they have “ instead of "). We should fix all quote characters in the wiki docs to be standard ASCII so they are pasteable and don't cause hard-to-track-down errors for people trying to copy-paste examples.This is a bit silly, and easy mistake to make when copy-pasting things around - the biggest culprit for me is always MS Word that insists on converting standard " characters to fancy “ characters.
This was a great catch by @wrynearson .
Don't think there's any urgency, but would be good to fix at some point.
cc @tovari @szabozoltan69