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
Parts and references #330
Parts and references #330
Conversation
This gives us more freedom to implement custom features
1fc6756
to
c1aa78b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks really good, bravo! 🎉 I noticed one issue is that when you draw a white diamond association (shared association), it was showing up as a part property when it should be a reference property.
This can be part of another PR, but now that we have the two main types of properties for Blocks, I think we can either de-emphasize or remove completely Attributes and Operations. I guess it is technically possible for a Block to have these, but I don't think I have seen them added in practice. What do you think about us just removing them entirely from the BlockItem and the block property page?
I was a bit in doubt on the shared association. I'll change it accordingly. |
Removing attributes and operations is trivial now, since Block is a separate diagram item now, not inheriting from ClassItem. Isn't it custom to have attributes for, for example, (using American units here, we use Bar as unit for pressure 😃 ) |
Those would be added by a 3rd Property that we haven't created yet called a Value Property. To support those we would need to add some default ValueTypes and make it possible to add additional ones, since every value property is typed by a ValueType. |
Then we'd better remove attributes and operations, before they are misused. Or maybe keep attributes until we have ValueTypes in place? |
I would be ok with just removing them I think, and then once we get initial SysML support finished, we can come back in with additions like ValueTypes. |
Fair enough. Sounds like a simple change to me. |
I removed attributes and operations. |
PR Type
What kind of change does this PR introduce?
What is the current behavior?
No parts and references compartment in Block diagram
Issue Number: #138
What is the new behavior?
Parts and references are visible:
Does this PR introduce a breaking change?
NB. It looks like SysML elements are not visible in the tree view at all (!)