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
A constant defined with the !constant keyword can be overridden, hence is not constants anymore.
This is quite error prone since it allows to easily redefine a constant value in another file (while using includes).
If it is expected behavior, it would probably be interesting to be able to parametrize it to make it stricter (I did not find a way to do it)
workspace {
!constant MICHEL "michel"
!constant MICHEL "mimich"
model {
user = person ${MICHEL}
softwareSystem = softwareSystem "Software System" {
webapp = container "Web Application" {
user -> this "Uses"
}
container "Database" {
webapp -> this "Reads from and writes to"
}
}
}
views {
systemContext softwareSystem {
include *
autolayout lr
}
}
}
The second value of the constant MICHEL overrides the first one without issue.
Screenshot
No response
Code sample
No response
Configuration
No response
Severity
Minor
Priority
I have no budget and there's no rush, please fix this for free
More information
No response
The text was updated successfully, but these errors were encountered:
Thanks, yes, this is a known issue that's been taken advantage of over the years, so requires more than just fixing it. I'm planning on deprecating !constant (removing it in v3.0.0) and replacing it with something like !const and !var.
Description
A constant defined with the !constant keyword can be overridden, hence is not constants anymore.
This is quite error prone since it allows to easily redefine a constant value in another file (while using includes).
If it is expected behavior, it would probably be interesting to be able to parametrize it to make it stricter (I did not find a way to do it)
Steps to reproduce
Screenshot
No response
Code sample
No response
Configuration
No response
Severity
Minor
Priority
I have no budget and there's no rush, please fix this for free
More information
No response
The text was updated successfully, but these errors were encountered: