Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: throw an error if the front-token header is missing on a successful refresh response #267

Merged

Conversation

porcellus
Copy link
Collaborator

Summary of change

Now we throw an explicit error instead of letting the session state silently break.

Related issues

  • Discord discussions

Test Plan

Added new test case

Documentation changes

N/A

Checklist for important updates

  • Changelog has been updated
  • frontendDriverInterfaceSupported.json file has been updated (if needed)
    • Along with the associated array in lib/ts/version.ts
  • Changes to the version if needed
    • In package.json
    • In package-lock.json
    • In lib/ts/version.ts
  • Had run npm run build-pretty
  • Had installed and ran the pre-commit hook
  • Issue this PR against the latest non released version branch.
    • To know which one it is, run find the latest released tag (git tag) in the format vX.Y.Z, and then find the latest branch (git branch --all) whose X.Y is greater than the latest released tag.
    • If no such branch exists, then create one from the latest released branch.

Copy link

github-actions bot commented Oct 4, 2024

size-limit report 📦

Path Size
lib/build/bundleEntry.js 21.06 KB (+0.64% 🔺)

@porcellus porcellus merged commit a214ad5 into 20.1 Oct 4, 2024
3 of 4 checks passed
@porcellus porcellus deleted the feat/error_if_front-token_missing_on_refresh_success branch October 4, 2024 16:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant