Optimizing the development workflow
Having to manually generate the schema and then the SDK might be a bit annoying when you are making many changes in your app. Here are a few things we suggest doing:
- When you run the app, this process will take place automatically. It should be fast so it doesn’t bother developers.
- In the builder, when we detect changes that affect the SDK, we will have a visible indicator to regenerate the SDK, which you can easily trigger from there.
- In some cases, we might decide to trigger this automatically so the user doesn’t even have to care about this.
These things should significantly improve the developer experience, making it easier to work with the app. This will be more noticeable once we expose models and we start making changes to the models.
Tools for GraphQL
There are a few things I think would be beneficial to developers:
- Trigger the generation of the GraphQL schema and SDK
- Quick access to the Apollo Explorer, that opens in a tab in VS Code
- Installation of the official GraphQL extension in case you want to review the generated schema
Optimizing the development workflow
Having to manually generate the schema and then the SDK might be a bit annoying when you are making many changes in your app. Here are a few things we suggest doing:
These things should significantly improve the developer experience, making it easier to work with the app. This will be more noticeable once we expose models and we start making changes to the models.
Tools for GraphQL
There are a few things I think would be beneficial to developers: