5da0995531
* feat: implement BiDi automation client base (without full extension cutover). [run ci] * chore: implement suggestions from code review. [run ci] * update error text to be in line with documentation * address comments from code review * address comments from code review * make bidi, cdp, and both active protocols object enumerations to make the code easier to read * address additional comments from code review * fix errors from refactor * update firefox warning
GraphQL
The GraphQL layer that @packages/launchpad and @packages/app use to interact with @packages/server.
With the goal of type safety, several tools and abstractions are used. The technologies are:
- nexus-graphql library for generating GraphQL schema using TypeScript objects
- graphql-code-generator generate TypeScript types from
gqlqueries (for front-end consuming the API)
This tutorial demonstrates how to build a type-safe GraphQL app using the above technologies. It's a good place to start, to learn how and why each tool is used.
Development
You will generally develop this in parallel with a front-end, in this case @packages/launchpad. Run yarn dev in @packages/launchpad and it will start up the GraphQL server. This also re-generates the graphql.schema file based on the declarations inside of entities.
Visit http://localhost:52200/graphql for the GraphiQL interface.
You can also develop in a test-driven manner using the tests.
yarn test-unitfor the unit testsyarn test-integrationfor the integration tests
Debugging
Logs available at cypress-verbose:graphql:* namespaces {fields,operation}