oslabs-beta / graphql-blueprint Goto Github PK

Currently top bars are main nav and tabs, we'd like to setup React Router to merge the bars like how the new UI design is mocked up:

When viewing databases or tables, we'd like to implement a title bar which will provide context to what's being viewed as well as any additional actions that view may have (like the options for graph or grid view). Screenshots for more context below:

• Understand the state of of one project

If we could implement the ability for users to include their REST API credentials and parameters, we could build it into our boilerplate generator for easy export of GraphQL queries and mutations.

• 1.
• 2.
• 3.

• 1. Review codebase

• 1. Review codebase

Our network requests total about 3mb - 2mb of which is all our dependency packages in the file, vendor.js. For now, I believe this is as compressed as possible with sideEffects: false. Either way, in slow connections, a cool loading screen that uses our "Info/Welcome <dialogue /> screen" and a spinning wheel?

• 1.
• 2.
• 3.

Currently still using the old GQL Designer design. Need to update to match new look + feel.

Adding a relation field to a Mongo database gives the error:

Uncaught TypeError: object is not iterable (cannot read property Symbol(Symbol.iterator))

at schemaReducer.js:337

• 1. Database component
• 2. Sidebar component
• 3. Grid view

Once we hook projects up to remote database (assigned to user auth feature), we can build a script to track unsaved changes using local storage. The component will prompt users to connect and query the database to update their project file.

• 1. Setup Git Permissions
• 2. Implement CircleCI

npm run test would not run so the solution was creating and setting up a babel.config.js file, installing the following dependencies: @babel/core & @babel/preset-env.
Also bumping jest version to 24.9.0.

• 1. Go through backend code, figure out what needs to be modified.
• 2. Set up buildForMultiple function in index.js
• 3. Write function for determining single vs. multiple databases
• 4. Modify utl files for multiple databases

• 1.
• 2.
• 3.

More exploration needed

After merging in @kevinberlanga's auth features, we'll want to rebuild the UX for how new projects are created and previously made projects are edited. The following screenshots show our intention:

• 1.
• 2.
• 3.

New screenshots and GIFs are needed for documentation and in app tips.

Tree view is a good way to have a birds eye view of the schema as a graph. Adding more color/styles to this will make it easier to look at and perhaps providing more navigation options in the window will enhance UX. Currently, tree view looks like: