fix: using enum instead of strings for auth step types

[jcaleb4]

Pull Request Checklist

• Did you add new tests and confirm existing tests pass? (yarn test)
• Did you update relevant docs? (docs are found in the site folder, and guidelines for updating/adding docs can be found in the contribution guide)
• Do your commits follow the Conventional Commits standard?
• Does your PR title also follow the Conventional Commits standard?
• If you have a breaking change, is it correctly reflected in your commit message? (e.g. feat!: breaking change)
• Did you run lint (yarn lint:check) and fix any issues? (yarn lint:write)
• Did you follow the contribution guidelines?

---

PR-Codex overview

This PR primarily focuses on refactoring the authStep handling in the authentication components by replacing string literals with an AuthStepType enum for improved type safety and maintainability.

Detailed summary

• Introduced AuthStepType enum to replace string literals in setAuthStep calls.
• Updated multiple components to use AuthStepType for various authentication steps.
• Ensured consistent handling of authStep types across the application.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
aa-sdk-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 13, 2025 5:28pm
aa-sdk-ui-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 13, 2025 5:28pm

[graphite-app]

How to use the Graphite Merge Queue

Add the label graphite-merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[moldy530]

What's the motivation for this change? we use string consts in other places of the code base and actually use enums fairly sparingly

[moldy530]

nit: for the enum name, can we do capital case? ie EmailVerify

[jcaleb4]

change is done

[jcaleb4]

@moldy530 my motivation for this PR is just that while working around the auth flow I felt the need to unify the source of the auth steps, I know it may be an opinionated change, but one of the advantages of using TS is that we can centralize these kind of things.

In my personal experience, using strings (specially in big teams) gets to be really messy at some point and takes out several advantages of using TS with enums:

• Type safety
• readability and self-documentation
• maintainability
• intelisense support
• consistency

I know there are several other places where you're using strings instead of enums, I just wanted to propose making this change because it makes sense to me; this is not required or anything, it is just me thinking that enums in this particular case would be a better use