Project 16 Summary

We added a real openapi and graphql definitions for Github API and they are too huge(more than 220k of lines). Some of our features stop working properly and the page becomes unresponsable. So we decided to switch to small naive implementations of Github API to test how good our graphql docs is.

What made you smile?

• Editor works fine with 220k+ lines of code.
• It is easy to add Graphql schema to the project and get result.
• Two APIs works well with the sidebar.

What did you find confusing?

• When we added graphql schema and openapi to sidebar it was render 1k elements in sidebar, it was not usable
• When we add both openapi and graphql into types for the catalog. The generated sidebar doesn't have graphql operations unless we remove openapi from types video.
• Having to large openapi/graphql definitions slow down the application to the ground. It can't even build the project.
• We lost all our work because we had an committed changes but the PR was merged before we committed them.