Skip to content
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

Added Firestore.set(), fixed Firestore.update() #21

Merged
merged 2 commits into from
Oct 25, 2023
Merged

Conversation

alexiglesias93
Copy link
Member

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of fireworkers in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.2.0 or ~0.2.0. See npm's documentation about semver for more information.

  • feat: add new Firestore.set() method that matches the behavior of the SDK's setDoc.
  • fix: update Firestore.update() to match the behavior of the SDK's updateDoc:
    • Fields will be merged instead of overriding the entire document.
    • Operations will fail if the document doesn't exist.

Closes #19

@alexiglesias93 alexiglesias93 self-assigned this Oct 25, 2023
@alexiglesias93 alexiglesias93 added the enhancement New feature or request label Oct 25, 2023
@alexiglesias93 alexiglesias93 merged commit 5be6e99 into master Oct 25, 2023
1 check passed
@alexiglesias93 alexiglesias93 deleted the update-set branch October 25, 2023 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

update action will clear all other fields except the ones provided
1 participant