-
Notifications
You must be signed in to change notification settings - Fork 61
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
[cleanup] Improve identification of view representation descriptions #1876
[cleanup] Improve identification of view representation descriptions #1876
Conversation
4d92431
to
aaa67c9
Compare
5b9436c
to
24e9afc
Compare
4ac8a83
to
2b215f2
Compare
CHANGELOG.adoc
Outdated
@@ -11,6 +11,7 @@ | |||
|
|||
=== Breaking changes | |||
|
|||
- https://github.com/eclipse-sirius/sirius-components/issues/1860[1860] [view] Changed the type of descriptionId of Node and Edge from UUID to String |
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.
Please add your entries to the end of their section, not the beginning. On top of that, this change is not related to view but diagram and will thus impact every user of the diagram component.
.filter(IDiagramContext.class::isInstance) | ||
.map(IDiagramContext.class::cast) | ||
.ifPresent(diagramContext -> diagramContext.getViewCreationRequests().add(viewCreationRequest)); |
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.
Do not change the indentation of the existing code
nodeMappingUUID, this.createNodeDescription(nodeMappingUUID), | ||
containerMappingUUID, this.createNodeDescription(containerMappingUUID) | ||
); | ||
); |
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.
Do not change the indentation of the existing code
nodeMappingUUID, this.createNodeDescription(nodeMappingUUID), | ||
containerMappingUUID, this.createNodeDescription(containerMappingUUID) | ||
); | ||
); |
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.
Do not change the indentation of the existing code
sourceContainerMappingUUID, this.createNodeDescription(sourceContainerMappingUUID), | ||
targetContainerMappingUUID, this.createNodeDescription(targetContainerMappingUUID) | ||
); | ||
); |
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.
Do not change the indentation of the existing code
public ViewService(IDocumentRepository documentRepository, EPackage.Registry ePackageRegistry) { | ||
private final IdDiagramProvider idProvider; | ||
|
||
public ViewService(IdDiagramProvider idProvider, IDocumentRepository documentRepository, EPackage.Registry ePackageRegistry) { |
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.
Try to keep the coherence in the order of the parameters / fields
* | ||
* @author mcharfadi | ||
*/ | ||
public interface IIdDiagramProvider { |
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 should probably be named IDiagramIdProvider
if (description instanceof DiagramDescription diagramDescription) { | ||
return this.idProvider.getIdDiagramDescription(diagramDescription); | ||
} | ||
|
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.
Here, we have something odd, the only goal of this method is to filter one representation description in a list of representation description to find the right one.
The real behavior that we want is instead to detect that the representation description has one of the new identifier and thus find the right one without having to look in all representation descriptions.
* | ||
* @author mcharfadi | ||
*/ | ||
public class IdDiagramProviderTest { |
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.
You need to many mocks and small stuff to have an efficient test here. This will be very brittle. Add an assertion on a test of the converter for example.
// DiagramElementDescription should have a proper id. | ||
return UUID.nameUUIDFromBytes(EcoreUtil.getURI(diagramElementDescription).toString().getBytes()).toString(); | ||
}; | ||
private final Function<org.eclipse.sirius.components.view.DiagramElementDescription, String> idDiagramElementProvider; |
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'm not sure that you need to keep that and the diagram id provider above. Keep one only
cb3e909
to
41951eb
Compare
…tring Signed-off-by: Michaël Charfadi <[email protected]>
41951eb
to
2383435
Compare
…iption elements Signed-off-by: Michaël Charfadi <[email protected]>
…and Edge Signed-off-by: Michaël Charfadi <[email protected]>
2383435
to
b5a32d0
Compare
Bug : #1860
Pull request template
General purpose
What is the main goal of this pull request?
Project management
priority:
andpr:
labels been added to the pull request? (In case of doubt, start with the labelspriority: low
andpr: to review later
)area:
,difficulty:
,type:
)CHANGELOG.adoc
been updated to reference the relevant issues?CHANGELOG.adoc
? (Including changes in the GraphQL API)CHANGELOG.adoc
? For example indoc/screenshots/2022.5.0-my-new-feature.png
Architectural decision records (ADR)
[doc]
?CHANGELOG.adoc
?Dependencies
CHANGELOG.adoc
?CHANGELOG.adoc
?Frontend
This section is not relevant if your contribution does not come with changes to the frontend.
General purpose
Typing
We need to improve the typing of our code, as such, we require every contribution to come with proper TypeScript typing for both changes contributing new files and those modifying existing files.
Please ensure that the following statements are true for each file created or modified (this may require you to improve code outside of your contribution).
useMutation<DATA_TYPE, VARIABLE_TYPE>(…)
useQuery<DATA_TYPE, VARIABLE_TYPE>(…)
useSubscription<DATA_TYPE, VARIABLE_TYPE>(…)
useMachine<CONTEXT_TYPE, EVENTS_TYPE>(…)
useState<STATE_TYPE>(…)
?.
(if the GraphQL API specifies that a field cannot benull
, do not treat it has potentiallynull
for example)let diagram: Diagram | null = null;
)Backend
This section is not relevant if your contribution does not come with changes to the backend.
General purpose
Architecture
Review
How to test this PR?
Please describe here the various use cases to test this pull request