-
-
Notifications
You must be signed in to change notification settings - Fork 55
Add test to verify StoredValue persistence across instances #75
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
base: main
Are you sure you want to change the base?
Conversation
Fixes for chained operations and allowing SecurelyStoredValue to remove values with shape changes
Boutique 3.0 beta 1
Fix: Strategy based removal on insert operates on all items rather than just inserted items
…fied when a Store is loaded
|
Hey @Salander7, thank you so much for the contribution! I'm currently on my honeymoon so realistically I won't be able to look at this too in depth until I'm back closer to the end of the month, but at a glance this looks like a good idea and the right idea. Before merging this in could I ask you to add a similar test for Thank you so much! |
|
Thank you for the feedback! I've added a test for @SecurelyStoredValue following the same pattern. Enjoy your honeymoon! 🎉 |
I added a new test that verifies @Storedvalue properly persists data across multiple instances.
The test verifies that:
This helps ensure the persistence behaviour of @Storedvalue works as expected when the same key is used in different places.