feat(core): added ability to specify dependencies for catalogs #1033
Conversation
🦋 Changeset detectedLatest commit: 83e483d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Yeah good question. This is to handle a usecase around multi-catalog configurations into one master one. Team A have a catalog in their repo, and they consume an Event from Team B, today they have to document this, but they do not own it This gives the users the ability to "mock" out events that they may need. in this case Team A would mock the event, they know they are using, but don't own the contract or docs for it.... (if that makes sense) |
From #930, added the ability to create catalog
dependencies. These are resources that a team may need for there catalog, but not necessarily own themself.By specifying a
dependencyEventCatalog will create these resource types for the teams allowing them to use EventCatalog with resources that are external.