Add support for custom field names and custom schema #109
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.
We are migrating to mongoose but our
deletedBy/At
fields have different names and for legacy reasons, we can not change this right now. We also need the ability to use a custom getter to transform our value.This PR will added support for
deletedBy
anddeletedAt
deletedBy
anddeletedAt
(could make the currentdeletedByType
obsolete, can be replaced by{ deletedBy: { type: String } }
)?I was inspired by how mongoose handles the
timestamp
schema option. Let me know if you prefer another way. Will resolve issue #92