Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

relation archetypes in dynamic views #396

Unanswered
abalabchenkov asked this question in Q&A
Discussion options

Expected

I would expect that new relations archetypes feature would also work in dynmaic view, but it does not

Actual

Too many tokens, expected: [order:] <identifier> [description] at line 31: a --request-> b

Steps to reproduce

workspace {
 model {
 archetypes {
 https = -> {
 technology "HTTPS"
 }
 reqest = -> {
 tags request
 }
 response = -> {
 tags response
 }
 }
 a = softwareSystem "A"
 b = softwareSystem "B"
 a --https-> b "Makes APIs calls using"
 }
views {
 systemLandscape main {
 	include *
	 autoLayout tb
 }
 
 dynamic * demo {
 a --request-> b
 b --response-> a
 autoLayout tb
 }
 }
}

Version/build information

4.0.0

Severity

Minor

Priority

Low (I have no budget and there's no rush, please fix this for free)

More information

No response

You must be logged in to vote

Replies: 1 comment 1 reply

Comment options

If you unwrap what you're trying to do with archetypes in dynamic views, that isn't supported either ... i.e. adding tags isn't supported for relationships in dynamic views.

workspace {
 model {
 archetypes {
 https = -> {
 technology "HTTPS"
 }
 reqest = -> {
 tags request
 }
 response = -> {
 tags response
 }
 }
 a = softwareSystem "A"
 b = softwareSystem "B"
 a --https-> b "Makes APIs calls using"
 }
views {
 systemLandscape main {
 	include *
	 autoLayout tb
 }
 
 dynamic * demo {
 a -> b {
 tags request
 }
 b -> a {
 tags response
 }
 autoLayout tb
 }
 }
}
You must be logged in to vote
1 reply
Comment options

@simonbrowndotje Yes, you are right. Than it would be a feature request to consider. Styling is managed through tags, and different releationship styling mostly makes sense in dynamic and deployment views. These are the diagrams, where we usually need much more arrows to show having differerent meanings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
Converted from issue

This discussion was converted from issue #395 on April 03, 2025 05:27.

AltStyle によって変換されたページ (->オリジナル) /