feat: Support dynamic default values #527
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joshuat
force-pushed
the
josh/feat/dynamic-defaults
branch
from
f1b6bc5
to
78850b6
Compare
avaly
previously approved these changes
Aug 1, 2023
joshuat
force-pushed
the
josh/feat/dynamic-defaults
branch
from
78850b6
to
9310a49
Compare
avaly
force-pushed
the
josh/feat/dynamic-defaults
branch
from
9310a49
to
2c127e5
Compare
avaly
approved these changes
Aug 14, 2023
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This introduces the ability for users to provide a function that returns default values rather than an object with static values. This is useful when you're using an
_idvalue other than ObjectId and would like to keep the functionality of automatically generating an_idvalue on insert.We continue with the existing behavior of only applying the default value for a path when the path is not included in the insert. This isn't technically a breaking change since all schemas will continue to work as expected.
Closes: #18