Corpus Management UI - GraphQL/REST/Mocked data proof of concept
Proof of concept merge request diff
Proof of concept video demo
Goals
-
Verify with a Proof of Concept if it is possible to use GraphQL, REST, and mocked data using a single UI/Javascript library.
-
Verify that the transport layer can be abstracted in a way that allows easy transition from REST and mocked data to graphQL
Desired Outcome
- If both goals are validated, then we should be able to build out the desired UI and swap out the mock data for real data very easily. This would be regardless of whatever technology we use to communicate with backend.
Background
The Corpus Management epic backend is in a high level of flux since we are highly dependent on the Package team. Endpoint implementation plans are in flux. It is still undetermined if we will use a graphQL or REST endpoint, or both.
We also want to continue development in the meantime and present users with a UI with mocked data while backend development continues.
The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.