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

[2456, 2466, 2469, 2470] Fixes on reference widget #2478

Merged
merged 5 commits into from
Oct 24, 2023

Conversation

frouene
Copy link
Contributor

@frouene frouene commented Oct 18, 2023

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?

cy.getByTestId('selected').findByTestId('Entity2').should('exist');
});

it.only('check widget reference filter ancestor only for containment reference', () => {
Copy link
Member

Choose a reason for hiding this comment

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

it.only should be removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

INVALID_INPUT = Invalid input type, "{0}" has been received while "{1}" was expected
UNEXPECTED_ERROR = An unexpected error has occurred, please contact the server administrator
INVALID_NUMBER = The new value "{0}" is not a valid number
UPPER_BOUNDARY_REACHED = Unable to create a new instance of "{0}" in feature "{1}" because it has reach its upper-bound cardinality."
Copy link
Member

Choose a reason for hiding this comment

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

The final " is not neeed; it shows as part of the message.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

@@ -39,12 +39,17 @@ public String unexpectedError() {

@Override
public String invalidInput(String expectedInputTypeName, String receivedInputTypeName) {
return this.messageSourceAccessor.getMessage("INVALID_INPUT", new Object[] { expectedInputTypeName, receivedInputTypeName });
return this.messageSourceAccessor.getMessage("INVALID_INPUT", new Object[]{expectedInputTypeName, receivedInputTypeName});
Copy link
Member

Choose a reason for hiding this comment

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

The Eclipse formatting profile keeps the spaces between [, {, etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done,
I've changed my format settings

@frouene frouene force-pushed the fro/fix/widget_ref_issues branch 3 times, most recently from a848385 to 52a14ca Compare October 23, 2023 15:16
@pcdavid
Copy link
Member

pcdavid commented Oct 23, 2023

I'll merge once the build is green.

…e from the reference widget

Bug: #2470
Signed-off-by: Florian ROUËNÉ <florian.rouene@obeosoft.com>
…et to a filtered item in the explorer

Bug: #2469
Signed-off-by: Florian ROUËNÉ <florian.rouene@obeosoft.com>
… reference widget

Bug: #2466
Signed-off-by: Florian ROUËNÉ <florian.rouene@obeosoft.com>
…o a mono reference no empty

Bug: #2456
Signed-off-by: Florian ROUËNÉ <florian.rouene@obeosoft.com>
…he option list in a reference widget modal transfert

Bug: #2487
Signed-off-by: Florian ROUËNÉ <florian.rouene@obeosoft.com>
@pcdavid pcdavid merged commit bd37f99 into master Oct 24, 2023
3 of 4 checks passed
@pcdavid pcdavid deleted the fro/fix/widget_ref_issues branch October 24, 2023 07:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment