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

[AAE-15727] add and modify columns for name in project table #1178

Draft
wants to merge 4 commits into
base: develop
Choose a base branch
from

Conversation

indrayanganguly
Copy link
Contributor

No description provided.

@CLAassistant
Copy link

CLAassistant commented Aug 11, 2023

CLA assistant check
All committers have signed the CLA.

@sonarcloud
Copy link

sonarcloud bot commented Aug 11, 2023

SonarCloud Quality Gate failed.    Quality Gate failed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 6 Code Smells

No Coverage information No Coverage information
39.7% 39.7% Duplication

idea Catch issues before they fail your Quality Gate with our IDE extension sonarlint SonarLint

Copy link
Contributor

@jsokolowskii jsokolowskii left a comment

Choose a reason for hiding this comment

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

Edit - changed review on @LorenzoDiGiuseppe comment, I think it has a good point.

Comment on lines 72 to +77
public void setName(String name) {
this.name = name;
setTechnicalName(name);

//TODO: Modify temporary code that sets display name same as technical name
setDisplayName(name);
}
Copy link
Contributor

Choose a reason for hiding this comment

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

I will leave just a comment since I will be off after today and I don't want to block the PR.
I think we should not set both names here, but just delegate to setTechnicalName. If it is required to set also the display name, I think it would be better doing it in another place to avoid having issues when get/set name will be deleted.
In addition, it would be easier implementing getName and setName with a default implementation in the interfaces to avoid repeating the same behavior.

Copy link
Contributor

@jsokolowskii jsokolowskii left a comment

Choose a reason for hiding this comment

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

Please check @LorenzoDiGiuseppe comment #1178 (comment)

Copy link
Contributor

@VitoAlbano VitoAlbano left a comment

Choose a reason for hiding this comment

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

This PR might actually be a super risk of breaking a lot of stuff , AS we pointed out in the ADR we discussed the first step is to add only the getDisplayName, not touching the getName.

@@ -50,7 +50,7 @@ public static ModelingNamingIdentifier<Project> projectNamed(String name) {
return new ModelingNamingIdentifier<Project>(name) {
@Override
protected String getName(Project project) {
return project.getName();
return project.getTechnicalName();
Copy link
Contributor

Choose a reason for hiding this comment

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

The step to renaming the getTechnicalName that is not the final name yet should be done in the end Why it's already here?

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.

7 participants