Closed matgaj closed 3 months ago
Hi @matgaj,
I think the parser skips over {...}
blocks. Those blocks normally refer to attributes assigned from stereotypes. This currently does not happen for attributes.
You can cheat a bit by defining it as - parent: Player = {readonly}
, then {readonly}
is assigned as default value.
@all-contributors please add @matgaj for idea
@danyeaw
I've put up a pull request to add @matgaj! :tada:
Describe the bug
Gaphor won't allow appending a read {readOnly} to a property.
To Reproduce
Expected behavior
Correct handling of attributes, as described on page 17 of the UML specification.
Screenshots
OS
Windows 11 Pro 23H2
Version
Version of Gaphor: 2.25.1
Additional information