e463fdbc61
* wip: system test to reproduce * system test for alsa stderr * split cypress from 3rd party stderr at parent process to electron child * rm garbage warning regexes * fix newline behavior when parsing internal stderr * migrate left over console errors * clean up system test name * fix typed import * extract stderr splitting to separate pkg so runner can use @packages/error * rm new err log from packherd-quire * handle backpressure * docs * some unit tests & coverage for stderr-filtering * unit tests * no longer test regexp specific output in spawn unit tests * filter enabled debug namespaces rather than just cypress namespacesc * revise stream splitting et al * try to fix v8 snapshot build?? * fix console.log assertion * add missing eslint config * rm unused spies * fix regexp for optional leading wsp and ansi on debug entries * update unit tests because sinon * lint * colon.. * build stderr-filtering before checking if binary exists * adds TagStream transform stream, fixes stderr from child proc config * add build-prod script for stderr-filtering * changelog * properly handle backpressure in prefixed content transform stream * use standard tsconfig? * better tsconfig * Add pkgStderrFiltering to monorepoPaths * add \"files\" manifest * pipe all stderr to stderr when CYPRESS_INTERNAL_DEBUG_ELECTRON is enabled * rm explicit build of stderr-filtering in check-if-binary-exists step * ensure all dependencies of scripts/ are built before scripts are executed in the check-if-binary-exists command * fix dev version ref * swap logic * add stdin piping * fix exec name on the run-on-dependencies command to be more useful * use correct env * rm obsolete type refs * simplify stderr-filtering public iface, pipe cy-in-cy stderr through filtering tx * bust cache * fix mocks * fix v8-snapshot * move stderrfiltering to dev pkg in cli * skip integrity check in ci, if they are out of date things should fail anyway * copypasta over a portion of stderr-filtering to cli, since cli cannot import @packages * Delete issues.md * rm special filtering for cy in cy * rm too narrow rules file --------- Co-authored-by: Jennifer Shehane <shehane.jennifer@gmail.com> Co-authored-by: Jennifer Shehane <jennifer@cypress.io> Co-authored-by: Bill Glesias <bglesias@gmail.com>
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}