Brightspot 4.5 will implement a new schema version diff feature. Since Brightspot's GraphQL schemas are automatically generated, it wasn’t always obvious what impact the changes that the Java Recordable and ViewModel classes had on the generated schema. Coupling this with the fact that Brightspot's GraphQL APIs are being consumed by applications outside of Brightspot, it was important to avoid breaking these clients as the Brightspot CMS APIs evolved. Allowing developers to visually see the impact of their Java code changes on the generated schema compared to a previous version helps prevent accidental backwards-incompatible changes from making their way into production environments.