One post tagged with "Schemas"

When someone opens a schema in your catalog, they rarely stop at the schema.

They want to know how to publish the message. Who else is consuming it. Which business flow it is part of. What changed since the version they integrated against.

Until now, most of those answers lived somewhere else in the catalog, or in someone's head.

EventCatalog 4.12 turns every schema into a page your consumers can work from.

This release (along with 4.11, which shipped the first part of this work) brings:

• A richer schema page: tabs for examples, producers and consumers, flows, versions, and details, all linkable.
• Written usage examples: explain how to use a message, with code in several languages, right next to the schema.
• Two new components: <Columns /> and <CodeGroup />, for any page in your catalog.
• No more .eventcatalog-core folder: EventCatalog now runs directly inside your project.
• Custom pages that match the rest of your catalog, and the assistant upgraded to AI SDK v7.