Skip to content

refactor(news_blocks_ui): remove shrinkwrap - #746

Merged
felangel merged 2 commits into
mainfrom
refactor/post-grid-shrinkwrap
Jan 24, 2023
Merged

felangel merged 2 commits into
mainfrom
refactor/post-grid-shrinkwrap

Conversation

@felangel

Copy link
Copy Markdown
Contributor

Description

  • refactor(news_blocks_ui): remove shrinkwrap

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

@kaiceyd kaiceyd left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

lgtm!

@felangel
felangel merged commit cf33c48 into main Jan 24, 2023
@felangel
felangel deleted the refactor/post-grid-shrinkwrap branch January 24, 2023 19:34
@felangel felangel linked an issue Jan 24, 2023 that may be closed by this pull request
),
)
.toList(),
LayoutBuilder(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is still not lazily laying out children, which is what is needed for a performant scrolling UI. The reason I did not refactor this myself is because it looks like it will require a much larger refactoring of this logic.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The PostGrid should never contain more than a handful of children but we can definitely do a larger refactor if you feel there would be a significant performance gain.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The PostGrid should never contain more than a handful of children

Is that asserted somewhere? What if the user provides hundreds of items? Or tweaks the code for their own use case and find themselves with a performance issue? I understand users of the toolkit are expected to use this code hands on and make changes.

I am just pointing this out for consideration since performance issues are very difficult for users to debug when the code is already provided to them.

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.

Remove uses of nested lists with "shrinkWrap: true"

3 participants