Update master before Moose 11 release #800
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-explicit 439 make all clients more explicit
…n-of-overriden-methods Fix #600.
Speed up #asMooseGroup by creating a storage that has the right size from the beginning
Speedup #asMooseGroup
A first Mermaid exporter
…entor-do-not-print-Object-properties 674 famix metamodel documentor do not print object properties
Only adding some class comments
I want to build a visualization starting with the "root" entities of a model (aka the entities without parent). To make this easy in the query browser I propose to introduce a #isRoot boolean property. I introduced it on TEntityMetalevelDependency since this is the trait bringing the concept of parents. While I tired to add tests I found out that we also had some root concept on MooseEntity but I think it is a bad idea to have it there because MooseEntity has no concept of parent. So I removed it. Fixes #679
…is already tested in the right place
Introduce #isRoot boolean property
Adding aggregations in the Roassal backend of UMLDocumentor
testGeneratorsAreUpToDate breaks easily and sometimes it's hard to know what is not up to date. Here I'm updating this test in order to improve the display of changes and to give the list of the changes in the description of the test failure
…e-printing Improve logs of testGeneratorsAreUpToDate
First iteration for better generated class comments
Add #displayFullString to have an equivalent of #mooseName also usefu…
…tings Add new icons: Drag-and-drop and Filter
Currently the parents of the stubs are not in the MooseModel which causes some inconsistances. Here is a fix. Related to #552
Smalltalk: Ensure all stubs are in the model
Allow to either import or import and install models
Improve importers API
Smalltalk attributes can be shared variable and we have a way to declare this. The problem is that this info can be lost when we flush the caches. This change fix this bug. I also declared this as a property in the MM so that we can query it in the query browser
Shared variable properties should be persisted
The Smalltalk importer is adding some properties to the methods but those are flushable. So either we need to make them permanent or to remove them. Since I've never seen anyone use those 2 propoerties I propose to remove them.
Remove unused MonticelloMethodVisitor. Merge AbstractSmalltalkMethodVisitor and SmalltalkMethodVisitor since there is now only one subclass. Some factorization of code
Clean SmalltalkMethodVisitor
Remove unused properties
…Named-to-FamixMetamodelGenerator 784 add methods new class named to famix metamodel generator
Generate Equality Check for entities
…assalBackend Add uses relationships as composition in FamixUMLRoassalBackend
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.