Changelog

We've resolved an issue where global editor keybindings were non-functional in the editor Docs tab. Previously, if you clicked an item inside the docs iframe, keybindings such as cmd+P were not processed correctly, opening the print dialog instead of the command palette. We've implemented a solution to mount keybinding listeners inside the docs, ensuring they are forwarded and processed by the editor.

We've introduced a new UI section to the billing page that enables users to view the amount of assistant credits they have.

We fixed an issue where updating data model schema caused numerous type errors during proposal creation. The errors were mainly due to improper configuration of relationships and permissions, which resulted in unnecessary file changes and schema modifications being proposed.

We have addressed an issue with the assistant's record generation feature that previously did not respect the specified model or the number of records requested. The improvement includes adding tests to ensure reliability, capping AI-powered record generation to 100, and refining logic to ensure it only creates related records when necessary.

We've enhanced the Shopify connection by adding the returns model.

The assistant can now manage certain queries before environment setup is complete. This improvement addresses issues where the assistant would ask for information, such as desired scopes for Shopify apps, but couldn't act on the response due to an incomplete setup.

We've made several updates to the credit purchase process. Users now have the option to upgrade to a paid plan and getting proposal credits or simply purchasing credits

• Further indentation for improved readability.
• Spacing out fields for better visual clarity.
• Placing all options and validations on one line, separated by commas.
• Updated relationships for consistency.

We have updated our default web app templates to include only React Router V7. For Shopify templates, both React Router V7 and Remix are available.
Web apps:

• RRv7 framework
• RRv7 declarative

Shopify apps:

• Remix SSR
• RRv7 declarative

We've implemented several design enhancements to the data viewer table, addressing key usability issues:

- Added the idea of an active column which is selected by the user and stays sticky while horizontally scrolling.
- Modified the blue highlight on the header to appear only when the cursor is exactly on the divider.
- Resolved issues with horizontal scrolling, ensuring smoother column rearrangements and preventing dark line overlap on the first column.

We've updated ggt to allow users to pull files directly from the production environment.

We've added the ability to apply filters to Shopify webhooks. Read Shopify's docs for more information on how to correctly format your filters: https://shopify.dev/docs/apps/build/webhooks/customize/filters

The `hasOne` relationship API ensures a 1-1 relationship is maintained when relinking records. Previously, unlinking a `hasOne` required either violating validation or removing the record. This improvement now handles these scenarios more gracefully without breaking required validations.

We addressed an issue where conflicts were occurring in GraphQL due to overlapping apiIdentifiers for model and global actions like deleteUser. Now, users will receive an error message if they attempt to create an action with a conflicting GraphQL mutation name, preventing such naming conflicts.

We've made several updates to the onboarding and template cards for the Shopify and BigCommerce integrations. Notable changes include:

• Updated the Shopify and BigCommerce onboarding connection card design.
• Aligned template cards with new design specifications.
• Removed unnecessary videos from the Shopify connection page.
• Replaced the Shopify connection installation prompt with a warning banner across multiple sections.

We've updated the behavior of links in previews so that they now change tabs within Gadget instead of opening a new browser tab.

The assistant UI now consolidates multiple package install changes into a single `package.json` file entry during change planning. Previously, each package installation generated a separate entry, causing clutter and confusion.

The empty state for chat has been updated for both development and production environments.

Development environment:

- "Add a blog feature to my app"
- "Explain this code"
- "Fix this error"

Production environment:

- "Explain this error"
- "Explain this code"
- "Why is this form crashing?"