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: remove old render method #7308

Merged
merged 1 commit into from
Jul 27, 2023
Merged

Conversation

BeksOmega
Copy link
Collaborator

@BeksOmega BeksOmega commented Jul 19, 2023

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 N/A

Proposed Changes

Removes the last vestiges of the old render management system.

Reason for Changes

Less variants!

Test Coverage

All tests pass. Smoke tested the playground and it looks good!

Also tested that hiding and showing the workspace works properly.

Documentation

N/A

Additional Information

Dependent on #7306 and #7307

@BeksOmega BeksOmega marked this pull request as ready for review July 26, 2023 22:05
@BeksOmega BeksOmega requested a review from a team as a code owner July 26, 2023 22:05
@github-actions github-actions bot added PR: fix Fixes a bug and removed PR: fix Fixes a bug labels Jul 26, 2023
this.toolbox_.position();
}
} else {
if (!isVisible) {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why is this one not needed? Setting the workspace visibility doesn't directly change the blocks or fields, so no rerender would be triggered.

Put another way: what case was this handling before?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I have no idea what case this was handling before. But I can't think of a reason it's needed now! I manually tested showing and hiding the workspace, and everything looks correct.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Dug into the blame, and the render existed originally when setVisible was implemented.: e8ab929 So maybe itw as necessary at some point? Or maybe it was just added cautiously.

I tested adding block to the workspace while the workspace was hidden, and that also works and renders things correctly. So I think this is safe to remove!

@BeksOmega BeksOmega merged commit 7118dd3 into google:develop Jul 27, 2023
10 checks passed
@BeksOmega BeksOmega deleted the fix/remove-render branch May 14, 2024 16:28
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.

2 participants