Make solution URI-safe when sending to API #28
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My correct solution for 2022 day 25 was failing when submitting through aocrunner. I know it was correct because submitting it manually on the website worked.
I suspect that the problem is that the solution isn't being URI encoded, and since the solution contained equals (
=
) characters, the answer was not properly received at the API end.This PR simply wraps the solution in
encodeURIComponent()
in the body of thePOST
fetch.I haven't confirmed that this is the reason it was rejecting my correct answer, but the solution should be URI encoded regardless.