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
Move core modelling concepts to a separate package #295
Conversation
a5c5f11
to
f4591d7
Compare
a2a279f
to
b6cbf2b
Compare
ec18578
to
f2978df
Compare
I think this is done, at least for the model. |
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.
I really really like this. I think this was a great idea to move some of the abstract elements and other core functionality out of the UML package 👍
No need to refer to UML in diagram module.
@amolenaar Windows builds are failing. I submitted an issue to help try to resolve it. |
PR Type
What kind of change does this PR introduce?
Part of #138.
What is the current behavior?
Evenrything is in
gaphor.UML
, which makes for no logical separation when extending Gaphor with other modelling types.What is the new behavior?
Element
Presentation
ElementFactory
Diagram
(it's aNamedElement
)Does this PR introduce a breaking change?