Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi! First of all, congratulations on this great library.
I was building a dynamic dashboard where users can add components based on the widgets they choose to display. During the implementation, I noticed there wasn’t a property available to define which component should be rendered (I’m persisting the grid state in localStorage).
I saw that there is already an open issue for this (#123), so I decided to add metadata support to grid items to address this limitation.
I also updated the playground example to verify that the metadata works correctly.
With this change, users can now attach and manage their own custom data within grid items.
Please let me know if you’d prefer me to revert the playground changes. I included them only to ensure everything was working as expected.