Integrate Auth to front end & move api documentation to our /docs page and remove scaler

[LEEDASILVA]

Docs API

Auth

logout

[LEEDASILVA]

This Pr also handles Graphql connection between the front service and the db. It allows us now to query the db with the right role (depending on the user logged in).

front/src/lib
├── auth.ts
├── equipment.ts
├── graphql-client.ts
├── locations.ts
└── utils.ts

1 directory, 5 files

each file indicates the queries and where we can fetch or add them. The graphql-client is basically the connection to the db via graphql engine ofc

[LEEDASILVA]

new pages for magic link:

Once clicked the user would receive email, this would be later on but you can see on the logs the link that we would click:

operafix_api  | FOR TESTING - magic link token: http://localhost:5173/api/auth/magic-link?token=7ad0585d0bb05e1ec78342cafd781b4ae976a77baf84c4343e49c9783e720ad9

once validated in 2 seconds we would be redirected to the home page

the link can be clicked again, any error would be displayed on the url:

- "/auth/error?reason=missing_token"
- "/auth/error?reason=server_error"
- "/auth/error?reason=invalid_token"

[LEEDASILVA]

added a /user route to manage users:

• managing users is only possible with admin role or location manager
• location manager can only manage add users from is own location
• admins are the only ones that can delete/deactivate the user (is_active to false)
• add new field on user table 'is_active' to allow soft delete
• fix sequential id increment when we seed the db
• creating users is also restricted from admin to location manager, location manager can only add employees or technicians not other roles, meanwhile admins can do whatever they want (except delete other admins)

[LEEDASILVA]

Added a way for the graphql requests/queries work with PWA offline! it allows the user to use the application even offline so queries would be cached for a while then refreshed once they have internet. This would allow them to submit issues of equipments even offline and it would be pushed once online.

For this had to add a schema.json with the graphql schema that would allow a better caching keys system. This was generated using npx -y get-graphql-schema -j -h "x-hasura-admin-secret=<sercrete>" http://localhost:8080/v1/graphql > src/lib/gql/schema.json

we should probably create a workflow to check if schema.json is updated compared to our database schema?

- name: Verify GraphQL schema is up to date
  run: |
    docker compose up -d postgres hasura
    npx -y get-graphql-schema -j -h "x-hasura-admin-secret=<sercrete>" http://localhost:8080/v1/graphql > src/lib/gql/schema.json
    git diff --exit-code src/lib/gql/schema.json \
      || (echo "Run 'npm run gql:introspect' and commit the result." && exit 1)

or should we add the npx -y get-graphql-schema -j -h "x-hasura-admin-secret=pNZxIfzAD43hka0HrR02JAmsZmLU10bI" http://localhost:8080/v1/graphql > src/lib/gql/schema.json to the package.json

{
  "scripts": {
    "gql:generate": "@urql/introspect-schema --header \"x-hasura-admin-secret=$HASURA_ADMIN_SECRET\" $VITE_GRAPHQL_URL --output src/lib/gql/schema.json",
    "gql:check": "git diff --exit-code src/lib/gql/schema.json"
  }
}

then we can just call it like this:

- name: Verify GraphQL schema is up to date
  run: |
    docker compose up -d postgres hasura
    npm run gql:generate
    git diff --exit-code src/lib/gql/schema.json \
      || (echo "Run 'npm run gql:introspect' and commit the result." && exit 1)