mirror of
https://github.com/appy-one/acebase.git
synced 2026-05-25 06:02:14 -06:00
[GH-ISSUE #207] When using "mutations" with a subscription it's throwing a warning #98
Labels
No labels
IndexedDB
browser
bug
dependencies
documentation
duplicate
enhancement
feature request
indexes
indexes
invalid
pull-request
query
question
transaction logging
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/acebase#98
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @diogomartino on GitHub (Mar 11, 2023).
Original GitHub issue: https://github.com/appy-one/acebase/issues/207
Originally assigned to: @appy-one on GitHub.
Hi! First of all, thanks for your work, this lib is awesome. I'm using NodeJS
v18.7.0with AceBase1.27.0.I'm trying to execute something when some specific props of an object change, and I'm trying to use subscriptions for this. But, while using code from the documentation, it's throwing a warning in the console:
It's throwing:
Unless you know what you are doing, it is best not to use the value of a mutations snapshot directly. Use child methods and forEach to iterate the mutations insteadWhat am I doing wrong? The lack of examples when using the "mutations" is making me quite confused, if that part could be improved it would be great.
Thanks!
@appy-one commented on GitHub (Mar 13, 2023):
Hi @diogomartino, thanks for reporting this. Kindly note that it is NOT throwing anything, it only logs a warning message to the console. In your case, it should not do this (you are using
forEachso that should be good). I checked the code and think I found the issue, I'll fix it asap!@diogomartino commented on GitHub (Mar 13, 2023):
Oh yes, I meant throwing as like a logging term, not like throwing an exception, you are correct. Thanks for seeing this 👍
@appy-one commented on GitHub (Apr 11, 2023):
@diogomartino I fixed this in
acebase-corev1.26.1, I'll publish a newacebasepackage shortly@appy-one commented on GitHub (Apr 11, 2023):
@diogomartino Fix has been published in https://github.com/appy-one/acebase/releases/tag/v1.28.0
@diogomartino commented on GitHub (Apr 15, 2023):
Thank you🙏