You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to request allowing add_or_update_field to selectively update a single element in the dictionary stored on Firebase. This function is specific to Godot 3.5, but I believe this applies to Godot 4's version as well.
Currently, if you have a dictionary or an array, updating must be done in a way roughly like this:
However, when working with nested structures, single document saves, or especially large dictionaries, this can result in some performance issues due to the sheer size of the update.
I'd like to request allowing a path to be provided to update something specifically, as such:
Which would allow the creator to track changes made since a prior save and then send updates only for those things specifically, significantly reducing the computational overhead.
As usual, thanks for the work you've done to keep this updated.
The text was updated successfully, but these errors were encountered:
I'd like to request allowing add_or_update_field to selectively update a single element in the dictionary stored on Firebase. This function is specific to Godot 3.5, but I believe this applies to Godot 4's version as well.
Currently, if you have a dictionary or an array, updating must be done in a way roughly like this:
document.add_or_update_field(word_experience, {가다: 6, 거기: 3, 기다리다: 1, 네: 6, 대: 6, 둘: 1, 먹다: 3, 멈추다: 3, 물: 28...)
However, when working with nested structures, single document saves, or especially large dictionaries, this can result in some performance issues due to the sheer size of the update.
I'd like to request allowing a path to be provided to update something specifically, as such:
document.add_or_update_field(word_experience.가다, 50)
Which would allow the creator to track changes made since a prior save and then send updates only for those things specifically, significantly reducing the computational overhead.
As usual, thanks for the work you've done to keep this updated.
The text was updated successfully, but these errors were encountered: