-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
HELP WANTED: Please test the new RxDB version 16 beta #6650
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon. Please update it or it may be closed to keep our repository organized. The best way is to add some more information or make a pull request with a test case. Also you might get help in fixing it at the RxDB Community Chat If you know you will continue working on this, just write any message to the issue (like "ping") to remove the stale tag. |
Ping |
I encountered a weird issue where a query to rxdb cleared all the form values on one of my app pages.
It's repeatable and happens every time. And it's a blocker now for us. |
@radiantone Which RxDB version? Please log the observed query results and check. If it emits the wrong things please make a PR with a failing unit test. |
Hello everyone. The next major version of RxDB (version 16) is in beta mode. This version is mostly for fixing things that are confusing to RxDB users. If you have any other ideas for how to improve RxDB, please write a comment here.
Version 16 is compatible with already stored data in of RxDB version 15 for most RxStorage implementation. So migration will be easy. Only the node-filesystem RxStorage and the OPFS RxStorage will required people to migrate the data itself with the storage migration plugin.
Please help testing and report any issues that you may find.
Changes are listed up here.
To test the new version, install the latest RxDB npm package beta version.
If you find any problems, please report them here with the following info:
Thank you 🙏
The text was updated successfully, but these errors were encountered: