Skip to content
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

[4444] Allow multiple implementation of IEditingContextSaver & IEditi… #4445

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mcharfadi
Copy link
Contributor

@mcharfadi mcharfadi commented Jan 20, 2025

…ngContextLoader

Bug : #4444
Signed-off-by: Michaël Charfadi [email protected]

Pull request template

General purpose

What is the main goal of this pull request?

  • Bug fixes
  • New features
  • Documentation
  • Cleanup
  • Tests
  • Build / releng

Project management

  • Has the pull request been added to the relevant project and milestone? (Only if you know that your work is part of a specific iteration such as the current one)
  • Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
  • Have the relevant issues been added to the pull request?
  • Have the relevant labels been added to the issues? (area:, difficulty:, type:)
  • Have the relevant issues been added to the same project and milestone as the pull request?
  • Has the CHANGELOG.adoc been updated to reference the relevant issues?
  • Have the relevant API breaks been described in the CHANGELOG.adoc? (Including changes in the GraphQL API)
  • In case of a change with a visual impact, are there any screenshots in the CHANGELOG.adoc? For example in doc/screenshots/2022.5.0-my-new-feature.png

Architectural decision records (ADR)

  • Does the title of the commit contributing the ADR start with [doc]?
  • Are the ADRs mentioned in the relevant section of the CHANGELOG.adoc?

Dependencies

  • Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
  • Are the new dependencies justified in the CHANGELOG.adoc?

Frontend

This section is not relevant if your contribution does not come with changes to the frontend.

General purpose

  • Is the code properly tested? (Plain old JavaScript tests for business code and tests based on React Testing Library for the components)

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).

  • Variables have a proper type
  • Functions’ arguments have a proper type
  • Functions’ return type are specified
  • Hooks are properly typed:
    • useMutation<DATA_TYPE, VARIABLE_TYPE>(…)
    • useQuery<DATA_TYPE, VARIABLE_TYPE>(…)
    • useSubscription<DATA_TYPE, VARIABLE_TYPE>(…)
    • useMachine<CONTEXT_TYPE, EVENTS_TYPE>(…)
    • useState<STATE_TYPE>(…)
  • All components have a proper typing for their props
  • No useless optional chaining with ?. (if the GraphQL API specifies that a field cannot be null, do not treat it has potentially null for example)
  • Nullable values have a proper type (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

  • Are all the event handlers tested?
  • Are the event processor tested?
  • Is the business code (services) tested?
  • Are diagram layout changes tested?

Architecture

  • Are data structure classes properly separated from behavioral classes?
  • Are all the relevant fields final?
  • Is any data structure mutable? If so, please write a comment indicating why
  • Are behavioral classes either stateless or side effect free?

Review

How to test this PR?

Please describe here the various use cases to test this pull request

  • Has the Kiwi TCMS test suite been updated with tests for this contribution?

@@ -40,6 +41,11 @@ public ViewerProjectDataFetcher(IProjectApplicationService projectApplicationSer
@Override
public ProjectDTO get(DataFetchingEnvironment environment) throws Exception {
String projectId = environment.getArgument(PROJECT_ID_ARGUMENT);
var normalizedId = projectId.split("\\+");
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would probably need to use a dedicated API

@mcharfadi mcharfadi force-pushed the mch/enh/editing_context_saver_loader branch 4 times, most recently from cac2db5 to bb225ad Compare January 20, 2025 12:59
@mcharfadi mcharfadi force-pushed the mch/enh/editing_context_saver_loader branch from bb225ad to 2bfe4d5 Compare January 20, 2025 13:09
@mcharfadi
Copy link
Contributor Author

mcharfadi commented Jan 20, 2025

Note that it's possible to persist representation by modifying the save method of RepresentationMetadataPersistenceService to get the "base" project but this is too ugly without a dedicated API.
Also we would also need to update more services that uses the projectId in order to get the representationMetaData for handling diagrams properly.

In conclusion I think we need an API to retrieve the projectId from the editingContextId or put the projectId in the editingContext to allow working with representations.

@mcharfadi mcharfadi marked this pull request as ready for review January 27, 2025 13:11
@mcharfadi mcharfadi requested a review from sbegaudeau as a code owner January 27, 2025 13:11
@@ -43,9 +43,6 @@ public ViewerEditingContextDataFetcher(IEditingContextApplicationService editing
@Override
public DataFetcherResult<String> get(DataFetchingEnvironment environment) throws Exception {
String editingContextId = environment.getArgument(EDITING_CONTEXT_ID_ARGUMENT);
if (!this.editingContextApplicationService.existsById(editingContextId)) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to figure out if the editing context exists, why remove that?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The editingContext does not exist at this point we just assume that it will exist if a project exists.
So since the new editingContext does not match an existing project with this implementation, I'm not sure how to test this.

}

public void load(EditingContext editingContext, String projectId) {
public IEditingContext load(String editingContextId) {
var project = this.projectSearchService.findById(editingContextId);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

optionalProject and test that the optional is not empty otherwise return null

return editingContext;
}

public void toEditingContext(EditingContext editingContext, String projectId) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

toEditingContext? You already have an editing context just keep load

@@ -73,6 +97,11 @@ public void load(EditingContext editingContext, String projectId) {
this.editingContextProcessors.forEach(processor -> processor.postProcess(editingContext));
}

@Override
public boolean canHandle(String projectId) {
return new UUIDParser().parse(projectId).isPresent() && this.projectSearchService.existsById(projectId);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are you parsing the UUID? We have moved away from UUID based identifier for the project id

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm testing if the id is the id of a project and in this cas I'm keeping the current implementation

this.semanticDataUpdateService.updateDocuments(cause, projectId, documents, domainUris);
}

editingContextSavers.stream()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just pick the first one, not all of them


boolean canHandle(String projectId);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why projectId?

Comment on lines +187 to +190
public Builder id(UUID id) {
this.id = id;
return this;
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why?? Those changes are odd

Comment on lines +50 to +58
@Override
public void add(ICause cause, UUID semanticDataId, AggregateReference<Project, String> project) {
var semanticData = SemanticData.newSemanticData()
.id(semanticDataId)
.project(project)
.documents(Set.of())
.build(cause);
this.semanticDataRepository.save(semanticData);
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's no need for that

@@ -39,7 +40,12 @@ public SemanticDataSearchService(ISemanticDataRepository semanticDataRepository)

@Override
public Optional<SemanticData> findByProject(AggregateReference<Project, String> project) {
return this.semanticDataRepository.findByProjectId(project.getId());
return this.semanticDataRepository.findByProjectId(project.getId()).stream().findFirst();
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we will need to change that but I think that you are missing some concept to capture which semantic data to use for a given project, we need to find out how to keep this information in the database.

/**
* Used to create the semantic data.
*
* @author sbegaudeau
*/
public interface ISemanticDataCreationService {
void initialize(ICause cause, AggregateReference<Project, String> project);

void add(ICause cause, UUID semanticDataId, AggregateReference<Project, String> project);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can be removed but we will probably need to update the previous method to something like create which would return the created semantic data

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow multiple implementation of IEditingContextSaver & IEditingContextLoader
2 participants