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

[2288] Make IconLabel a react flow node #2305

Closed
wants to merge 1 commit into from

Conversation

gcoutable
Copy link
Contributor

@gcoutable gcoutable commented Aug 23, 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?

@gcoutable gcoutable added this to the 2023.10.0 milestone Aug 23, 2023
@gcoutable gcoutable linked an issue Aug 23, 2023 that may be closed by this pull request
@gcoutable gcoutable force-pushed the gco/enh/iconlabel-reactflow-node branch 2 times, most recently from 5314e5f to 01a5d51 Compare August 25, 2023 16:18
@gcoutable gcoutable force-pushed the gco/enh/iconlabel-reactflow-node branch from 01a5d51 to 364ccb8 Compare September 4, 2023 09:35
Copy link
Contributor

@mcharfadi mcharfadi left a comment

Choose a reason for hiding this comment

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

Maybe we could precise the node.extent to avoid the node being moved at the same position as the label of the parent node.

@gcoutable gcoutable force-pushed the gco/enh/iconlabel-reactflow-node branch 5 times, most recently from 8677b6d to 1504b35 Compare September 18, 2023 08:13
@gcoutable
Copy link
Contributor Author

Maybe we could precise the node.extent to avoid the node being moved at the same position as the label of the parent node.

With #288 node will be able to move anywhere, so, I think the node.extent will not be used at all

@mcharfadi mcharfadi self-requested a review September 18, 2023 09:05
@mcharfadi
Copy link
Contributor

mcharfadi commented Sep 18, 2023

I'm not able to hide the Icon Label Nodes, if we can't hide them we should not have the action in the toolbar.

@gcoutable gcoutable force-pushed the gco/enh/iconlabel-reactflow-node branch from 1504b35 to 2fdc6c0 Compare September 18, 2023 13:15
@mcharfadi mcharfadi self-requested a review September 18, 2023 13:31
Copy link
Contributor

@mcharfadi mcharfadi left a comment

Choose a reason for hiding this comment

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

There is a small issue regarding layout when hiding all the IconLabel of a node
https://github.com/eclipse-sirius/sirius-web/assets/121878084/446a8af6-27c3-4b42-a528-8ce8467d6001

@gcoutable
Copy link
Contributor Author

There is a small issue regarding layout when hiding all the IconLabel of a node https://github.com/eclipse-sirius/sirius-web/assets/121878084/446a8af6-27c3-4b42-a528-8ce8467d6001

A fix to that issue is included in the next PR.
We may merge the next PR (which can include this one) directly

@sbegaudeau sbegaudeau modified the milestones: 2023.10.0, 2023.12.0 Oct 2, 2023
@gcoutable gcoutable force-pushed the gco/enh/iconlabel-reactflow-node branch 2 times, most recently from 9e2c363 to 75de2f1 Compare October 9, 2023 13:12
@mcharfadi mcharfadi force-pushed the gco/enh/iconlabel-reactflow-node branch from 305015a to 2c442c6 Compare October 10, 2023 07:18
Bug: #2288
Signed-off-by: Guillaume Coutable <guillaume.coutable@obeo.fr>
@gcoutable
Copy link
Contributor Author

I am closing this PR because it includes layout regressions that have been fixed in the next PR (#2315), and #2315 includes the commit from this PR.
I have done that to prevent the staging instance from having a state with an issue.

@gcoutable gcoutable closed this Oct 10, 2023
@gcoutable gcoutable deleted the gco/enh/iconlabel-reactflow-node branch October 10, 2023 16:01
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.

Make list items reactflow nodes
3 participants