Add Type Safety for GraphQL Error Extensions Code

[samyakpiya]

References

This issues is a follow up from PR #9288. For more context, check this conversation.

Issue

Currently, there is no type-safe mechanism for handling GraphQL error extensions codes on the frontend. This creates a risk of runtime errors and makes the code harder to maintain.

Context

In the handleChallenge function, an error code (EMAIL_NOT_VERIFIED) from the backend is used to redirect users to the email verification page. However, the implementation lacks type safety. Adding type safety will help ensure consistency and prevent errors when checking these codes.

Relevant code snippet from the current implementation:

if (
  error instanceof ApolloError &&
  error.graphQLErrors[0]?.extensions?.code === 'EMAIL_NOT_VERIFIED'
) {
  setSearchParams({ email });
  setSignInUpStep(SignInUpStep.EmailVerification);
  throw error;
}

Proposed Solution

To address this, create a shared file to store error codes in the twenty-shared package. This will:

• Ensure error codes are centrally defined and reusable.
• Provide type safety for both frontend and backend when working with these codes.

[samyakpiya]

Closing as this has been moved to the core team and is a duplicate.