freddydumont / green-list-redwood Goto Github PK

Inspiration

Finish the sign up form and integrate with backend

Reuse types from previous codebase and convert new code

A field should be added to the user profile that corresponds to data understood by the selected date picker library

The query string should be updated to match

• Sort
• Filter
• Pagination

Right now, the locales are loaded with the i18next-xhr-backend package and React Suspense as suggested by this guide.

This approach breaks when some other data is fetched and takes precedence. This data's spinner will display, then a with flash from <Suspense fallback={null}> while it loads the locales:

It should present the user with their current information and a way to change them.

https://kentcdodds.com/blog/make-your-own-dev-tools

Fuzzy search for all fields

Create a GraphQL mutation for form submission. It should:

• validate the whole form object
• store new user + profile
• return success or error object

Everything related to session management

A sub menu of the user dashboard should allow them to change their calendar availability.

The email should contain a magic link to authenticate and update calendar availabilities

The staging database should be seeded with a number of users, with randomized:

• skills
• availabilities
• confirmation state
• calendar availability

Issues related to content or translation.

Page for authenticated users to manage their calendar availabilities

Email field -> magic link -> open link in browser -> auth complete -> redirection to /admin (ADMIN) or /profile (USER)

• unauthenticated request should be redirected
• unauthorized user should be redirected to /profile

Issues relating to the Database and API

The ids for skills, categories and availabilities are hard coded into the validation schema.

The validation schema should be generated after the GraphQL query runs: generateValidationSchema(ids).

• replace schemas with functions that accept ids and return schema
• create a query to get the ids from the db
• implement for skills and availabilities

Obtain the final list of skills to be seeded in the database

When logging in, all that's needed is an email. If we can avoid a potentially pricy auth provider that'd be the best solution.

Redwood is actively working on integrating Netlify Identity and Auth0.

Auth0 would be much more advantageous for us thanks to its generous free tier (7k free users). We could start with that, and roll out our own solution in the future if we ever reach the 7k limit.

Simple box with email field for passwordless auth

The form is a SPA, so going back using the browser will lead to potentially unexpected results.
We should warn the user that data will be lost before they attempt navigation.

formMachine.js has a guard called warnBeforeExit that can be used for that purpose. The issue is in triggering it via back button detection.

• Separate User and Profile
• Create role enum on user
  • ADMIN
  • USER

• Add adminNotes model in database schema
• Create mutation for adding a note
• Display a note field in the table view

When a user initially selects their availability or updates them, it should be reflected in the database. We can use prisma's upsert in a graphql mutation.

Warn user, clear the form state and go back to the home page

Individual pages are validated on the front end. When the user submits the form, the submitted data should also be validated before writing to the database.

• Validate data
• Handle returned validation errors on front end

• Refactor error messages to accept intl keys rather than calling the intl function (i18next.t('form:validation.firstname')) in the validation schemas
• Create workspace and move code there
• Import in web, make sure it still works

use a date picker library

It overwrites the files and eliminates dynamically generated ids.

When selecting skill categories, the content below (textarea and checkbox) is pushed over the FromButtonWrapper:

All content must be validated and translated into French by stakeholders. This can be started when the form is mostly complete.