GraphQL API

[Arcath]

Checklist

• TypeDef generation
• Resolver generation
• API Secret Management
• API Docs

Summary

This will likely be the breaking change for version 3, running the API under its own container.

This is proving a fun challenge, the typedefs and resolvers need to be dynamically generated. The API is no use to someone if they have to lookup and asset and its fields etc... they want to use their own assets etc...

This will take a fair bit of work, this PR will end up a bit of a notepad

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	13.05%	286 / 2191
🔵	Statements	12.99%	294 / 2262
🔵	Functions	8.58%	54 / 629
🔵	Branches	9.5%	54 / 568

File Coverage

No changed files found.

Generated in workflow #158 for commit 75ff917 by the Vitest Coverage Report Action

[Arcath]

API Keys

API Keys should come in 2 variants.

1. User generated long lived keys, show once and permission-able.
2. System generated short lived keys, possibly tied to the session? so the main app can make use of the API.

[Arcath]

Fields

Fields will need a gql handler as well, so that the data can be returned in a gql compatible way.

For example a relation field will need to return an array of IDs that then resolve into objects that match the type. Making the typeDef:

type Laptop {
  id: String
  asset: AssetRegister
}