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

fix: icons not having their locations updated #7012

Merged
merged 2 commits into from
Apr 24, 2023

Conversation

BeksOmega
Copy link
Collaborator

The basics

  • I branched from develop
  • My pull request is against develop
  • My code follows the style guide
  • I ran npm run format and npm run lint

The details

Resolves

Fixes #6999

Proposed Changes

Adds a step to the queued render process that updates the location of icons.

Reason for Changes

Elements of a block don't get to decide where they are positioned, but some of them (icons and connections) need to know where they're positioned. Before the code for updating icons was hidden inside moveConnections which was triggered via renderedConnection.tighten. Now it has been separated out so that it is clear what's happening.

Test Coverage

Just manual testing =(

Documentation

N/A

Additional Information

N/A

@BeksOmega BeksOmega requested a review from a team as a code owner April 24, 2023 19:28
@github-actions github-actions bot added the PR: fix Fixes a bug label Apr 24, 2023
@BeksOmega BeksOmega merged commit 139bc29 into google:develop Apr 24, 2023
BeksOmega added a commit that referenced this pull request Apr 26, 2023
* fix: icons not having their locations updated

* chore: fix running headful tests in node

(cherry picked from commit 139bc29)
@BeksOmega BeksOmega mentioned this pull request Apr 26, 2023
4 tasks
@BeksOmega BeksOmega deleted the fix/icon-locations branch April 26, 2023 16:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: fix Fixes a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bubbles (comments, warnings) attached to child blocks are not positioned correctly
2 participants