Opinionated SaaS quick-start with pre-built user account and organization system for full-stack application development in React, Node.js, GraphQL and PostgreSQL. Powered by PostGraphile, TypeScript, Apollo Client, Graphile Worker, Graphile Migrate, GraphQL Code Generator, Ant Design and Next.js
On the /settings page the error for the username being unique is not currently being handled correctly.
The check on errors coming back from Apollo is checking for the error code 23505 but it is actually being rewritten as NUNIQ and so does not match.
The error codes are stated in the error_codes.md file, replaced using the handleErrors.ts file and I can also confirm I am physically seeing NUNIQ being returned when using the starter.
Performance impact
None
Security impact
None
Checklist
[x] My code matches the project's code style and yarn lint:fix passes.
[ ] I've added tests for the new feature, and yarn test passes.
[ ] I have detailed the new feature in the relevant documentation.
[ ] I have added this feature to 'Pending' in the RELEASE_NOTES.md file (if one exists).
[ ] If this is a breaking change I've explained why.
Description
On the
/settingspage the error for the username being unique is not currently being handled correctly.The check on errors coming back from Apollo is checking for the error code
23505but it is actually being rewritten asNUNIQand so does not match.The error codes are stated in the error_codes.md file, replaced using the handleErrors.ts file and I can also confirm I am physically seeing
NUNIQbeing returned when using the starter.Performance impact
None
Security impact
None
Checklist
yarn lint:fixpasses.yarn testpasses.RELEASE_NOTES.mdfile (if one exists).