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

Allow using unserializable components #173

Merged
merged 28 commits into from
Feb 7, 2025

Conversation

tamasmak
Copy link
Contributor

Closes #141

@tamasmak tamasmak self-assigned this Jan 29, 2025
@tamasmak tamasmak changed the title [DRAFT] Allow using unserializable components Allow using unserializable components Feb 5, 2025
@tamasmak tamasmak marked this pull request as ready for review February 5, 2025 07:52
@tamasmak tamasmak requested a review from mcollovati February 5, 2025 08:03
Copy link
Contributor

@mcollovati mcollovati left a comment

Choose a reason for hiding this comment

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

Added some minor comments, but overall LGTM

mcollovati
mcollovati previously approved these changes Feb 5, 2025
Copy link
Contributor

@mcollovati mcollovati left a comment

Choose a reason for hiding this comment

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

I did not yet test on a clustered environment, but LGTM

@mcollovati mcollovati dismissed their stale review February 5, 2025 15:16

I did a test in a local cluster with the Spreadsheet component, and unfortunately, it seems there's that doesn't work. When switching node, the contents of the spreadsheet are not restored.
I need to do additional tests

@tamasmak tamasmak merged commit f636cf7 into main Feb 7, 2025
2 checks passed
@tamasmak tamasmak deleted the feat/141-allow-using-unserializable-components branch February 7, 2025 14:16
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.

Add UnserializableComponentWrapper to allow using unserializable components
2 participants