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

Add server-side valid metadata value services #7405

Merged
merged 3 commits into from
Feb 8, 2023

Conversation

mandy-chessell
Copy link
Contributor

Signed-off-by: Mandy Chessell [email protected]

Description

This PR:

  • extends the valid metadata values client interface for the Open Metadata Store framework services to include the ability to control the values in map attributes (such as additionalProperties).
  • adds the server side implementation for all valid metadata values operations
  • adds postman collection for these operations
  • extends Asset Owner FVT to include tests for these new methods.

Related Issue(s)

None

Testing

New FVT tests and use of postman to verify the function

Release Notes & Documentation

Changes already made to egeria-docs

Additional notes

Copy link

@github-advanced-security github-advanced-security bot left a comment

Choose a reason for hiding this comment

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

CodeQL found more than 10 potential problems in the proposed changes. Check the Files changed tab for more details.

@mandy-chessell mandy-chessell merged commit f74e440 into odpi:main Feb 8, 2023
throw new FVTUnexpectedCondition(testCaseName, activityName + " has bad display name of " + validMetadataValue.getDisplayName());
}

if (! "A controlled validation of the efficacy of a particular treatment with selected patients.".equals(validMetadataValue.getDescription()))
Copy link
Contributor

Choose a reason for hiding this comment

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

6% of developers fix this issue

YodaCondition: The non-constant portion of an equals check generally comes first.


Suggested change
if (! "A controlled validation of the efficacy of a particular treatment with selected patients.".equals(validMetadataValue.getDescription()))
if (! Objects.equals(validMetadataValue.getDescription(), "A controlled validation of the efficacy of a particular treatment with selected patients."))

ℹ️ Expand to see all @sonatype-lift commands

You can reply with the following commands. For example, reply with @sonatype-lift ignoreall to leave out all findings.

Command Usage
@sonatype-lift ignore Leave out the above finding from this PR
@sonatype-lift ignoreall Leave out all the existing findings from this PR
@sonatype-lift exclude <file|issue|path|tool> Exclude specified file|issue|path|tool from Lift findings by updating your config.toml file

Note: When talking to LiftBot, you need to refresh the page to see its response.
Click here to add LiftBot to another repo.


Help us improve LIFT! (Sonatype LiftBot external survey)

Was this a good recommendation for you? Answering this survey will not impact your Lift settings.

[ 🙁 Not relevant ] - [ 😕 Won't fix ] - [ 😑 Not critical, will fix ] - [ 🙂 Critical, will fix ] - [ 😊 Critical, fixing now ]

throw new FVTUnexpectedCondition(testCaseName, activityName + " returned null");
}

if (! "Clinical Trial".equals(validMetadataValue.getDisplayName()))
Copy link
Contributor

Choose a reason for hiding this comment

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

6% of developers fix this issue

YodaCondition: The non-constant portion of an equals check generally comes first.


Suggested change
if (! "Clinical Trial".equals(validMetadataValue.getDisplayName()))
if (! Objects.equals(validMetadataValue.getDisplayName(), "Clinical Trial"))

ℹ️ Expand to see all @sonatype-lift commands

You can reply with the following commands. For example, reply with @sonatype-lift ignoreall to leave out all findings.

Command Usage
@sonatype-lift ignore Leave out the above finding from this PR
@sonatype-lift ignoreall Leave out all the existing findings from this PR
@sonatype-lift exclude <file|issue|path|tool> Exclude specified file|issue|path|tool from Lift findings by updating your config.toml file

Note: When talking to LiftBot, you need to refresh the page to see its response.
Click here to add LiftBot to another repo.


Help us improve LIFT! (Sonatype LiftBot external survey)

Was this a good recommendation for you? Answering this survey will not impact your Lift settings.

[ 🙁 Not relevant ] - [ 😕 Won't fix ] - [ 😑 Not critical, will fix ] - [ 🙂 Critical, will fix ] - [ 😊 Critical, fixing now ]

Objects.equals(title, that.title) &&
Objects.equals(instructions, that.instructions) &&
Objects.equals(category, that.category) &&
Objects.equals(dueDate, that.dueDate) &&
Copy link
Contributor

Choose a reason for hiding this comment

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

3% of developers fix this issue

UndefinedEquals: Subtypes of Date are not guaranteed to implement a useful #equals method.


ℹ️ Expand to see all @sonatype-lift commands

You can reply with the following commands. For example, reply with @sonatype-lift ignoreall to leave out all findings.

Command Usage
@sonatype-lift ignore Leave out the above finding from this PR
@sonatype-lift ignoreall Leave out all the existing findings from this PR
@sonatype-lift exclude <file|issue|path|tool> Exclude specified file|issue|path|tool from Lift findings by updating your config.toml file

Note: When talking to LiftBot, you need to refresh the page to see its response.
Click here to add LiftBot to another repo.


Help us improve LIFT! (Sonatype LiftBot external survey)

Was this a good recommendation for you? Answering this survey will not impact your Lift settings.

[ 🙁 Not relevant ] - [ 😕 Won't fix ] - [ 😑 Not critical, will fix ] - [ 🙂 Critical, will fix ] - [ 😊 Critical, fixing now ]

@sonatype-lift
Copy link
Contributor

sonatype-lift bot commented Feb 8, 2023

🛠 Lift Auto-fix

Some of the Lift findings in this PR can be automatically fixed. You can download and apply these changes in your local project directory of your branch to review the suggestions before committing.1

# Download the patch
curl https://lift.sonatype.com/api/patch/github.com/odpi/egeria/7405.diff -o lift-autofixes.diff

# Apply the patch with git
git apply lift-autofixes.diff

# Review the changes
git diff

Want it all in a single command? Open a terminal in your project's directory and copy and paste the following command:

curl https://lift.sonatype.com/api/patch/github.com/odpi/egeria/7405.diff | git apply

Once you're satisfied, commit and push your changes in your project.

Footnotes

  1. You can preview the patch by opening the patch URL in the browser.

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

Successfully merging this pull request may close these issues.

1 participant