Fixes .ROBLOSECURITY=
requirement when binding cookies
#21
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.
This pull fixes the requirement of prefixing your cookies with a
.ROBLOSECURITY
string when context binding them into a function, as in such an example:This package comes with all of the return type signatures for each API request, but fails to export them for convenience. This would fix #20.
I added a bare minimum test suite to verify the changes I was making:
/tests
I also added the
.name
property on HttpError.