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
Docs say this: "Anytime you update a document, the extension propagates the update to the corresponding Algolia record. If you delete a document, the extension removes the corresponding Algolia record."
I'm finding that when I update a firestore document property value, the extension correctly updates the corresponding Algolia record. However, if I update a firestore document value by setting that property value equal to null, this update is not propogated to the corresponding Algolia record. Could somebody else test this and confirm? Can't seem to pinpoint the disconnect between my firestore database and corresponding algolia index.
The text was updated successfully, but these errors were encountered:
@smomin Yeah, I realized it was more of a feature and not necessarily an issue/bug with the codebase. Ended up removing the extension and handling updates internally, so no need for any changes. Our personal use-case involved products; products that went off sale were not updated in the algolia index because that null value was not captured. In hind-sight, we could have restructured our code around setting the sale_price to 0 rather than null, but what's done is done haha
Docs say this: "Anytime you update a document, the extension propagates the update to the corresponding Algolia record. If you delete a document, the extension removes the corresponding Algolia record."
I'm finding that when I update a firestore document property value, the extension correctly updates the corresponding Algolia record. However, if I update a firestore document value by setting that property value equal to null, this update is not propogated to the corresponding Algolia record. Could somebody else test this and confirm? Can't seem to pinpoint the disconnect between my firestore database and corresponding algolia index.
The text was updated successfully, but these errors were encountered: