Whats new in EventCatalog - July 2025
Welcome to the monthly update for EventCatalog, here you can find what's next, how to get started, and what's coming next.
- EventCatalog Linter
- New Entity Resource and Entity Map
- Fetching Schemas at Runtime
- Better Search Capabilities (Search v2)
- Customize Your Documentation Pages (Detail Panel)
- Updated Ubiquitous Language Explorer
- AsyncAPI and OpenAPI Generator Enhancements
- Other project improvements
EventCatalog Linter
We're excited to introduce the EventCatalog Linter — a powerful tool to help you maintain consistency and quality across your architecture documentation. The linter helps catch common issues, enforces best practices, and ensures your EventCatalog stays well-organized as it grows.
The linter can be integrated into your CI/CD pipelines to catch issues early and maintain documentation standards across your team.
$ npx @eventcatalog/linter
services/user-service/index.mdx
✖ error version: Invalid semantic version format [version] (schema/valid-semver)
⚠ warning Summary is required for better documentation [summary] (best-practices/summary-required)
✖ 2 problems
domains/sales/index.mdx
✖ error Referenced service "order-service" does not exist [services] (refs/resource-exists)
✖ 1 problem
✖ 3 problems (2 errors, 1 warning)
2 files checked
To get started with the EventCatalog Linter, you can read our quick guide in our documentation here.
New Entity Resource and Entity Map
We've introduced Entity Resources and the new EntityMap component to help you document and visualize your domain entities and their relationships. This new feature allows you to:
- Document your domain entities with rich metadata
- Visualize entity relationships across your architecture
- Track how entities flow through your systems
- Better understand your domain model
The Entity Map provides a visual representation of your domain entities and their relationships, making it easier to understand your domain model at a glance.
Using the EntityMap component you can embed the entity map into your documentation pages and pick and choose which entities to display.