-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Architecture/fix] Throw explicit error for invalid configuration causing overlapping nodes #6176
base: develop
Are you sure you want to change the base?
[Architecture/fix] Throw explicit error for invalid configuration causing overlapping nodes #6176
Conversation
…ne side of a service
…to 6120/architecture-node-overlap
|
✅ Deploy Preview for mermaid-js ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
commit: |
The latest updates on your projects. Learn more about Argos notifications ↗︎ Awaiting the start of a new Argos build… |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #6176 +/- ##
==========================================
- Coverage 4.47% 4.47% -0.01%
==========================================
Files 385 385
Lines 54190 54207 +17
Branches 598 598
==========================================
Hits 2425 2425
- Misses 51765 51782 +17
Flags with carried forward coverage won't be shown. Click here to find out more.
|
📑 Summary
To avoid user confusion, Architecture diagrams now explicitly throw an error if two services attempt to connect to the same side of another service.
Resolves #6120
📋 Tasks
Make sure you
MERMAID_RELEASE_VERSION
is used for all new features.pnpm changeset
and following the prompts. Changesets that add features should beminor
and those that fix bugs should bepatch
. Please prefix changeset messages withfeat:
,fix:
, orchore:
.