You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some users that want to relate resources together, not in a group (domain point of view), but this event (resource) related to this other event, or service etc.
It's just a way that users can group things up visually and let there own catalog users know what resources are related to each other.
Kind of like when you read a doc page and it says "You may also like...".
This would introduce a new field called **relatedResources**
---
id: Ordersname: Ordersversion: 0.0.1summary: | Domain that contains order related services and messages.owners:
- dboyneevents:
- id: OrderPlacedrelatedResources:
- id: OrderOwned
- id: OrderCreated
- id: PaymentService
- id: PaymentChannelbadges:
- content: Payment DomainbackgroundColor: bluetextColor: blue
---
Proposed Solution
No response
Implementation Notes
No response
Community Notes
Please vote by adding a 👍 reaction to the issue to help us prioritize.
If you are interested to work on this issue, please leave a comment.
If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out in the EventCatalog Discord.
The text was updated successfully, but these errors were encountered:
Use Case
I have some users that want to relate resources together, not in a group (domain point of view), but this event (resource) related to this other event, or service etc.
It's just a way that users can group things up visually and let there own catalog users know what resources are related to each other.
Kind of like when you read a doc page and it says "You may also like...".
This would introduce a new field called
**relatedResources**
Proposed Solution
No response
Implementation Notes
No response
Community Notes
The text was updated successfully, but these errors were encountered: