Is it possible to skip validation on a mongoose schema field if it has a default value?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have the following scenario: I need to create a document with a date. The date can be either a future date or a current date that is set by default by my schema. My validation looks like this:
function validateStartDate() {
const { startDate } = this;
return startDate.getTime() >= new Date().getTime();
}
This check fails if the default date is set by mongoose. So, I was thinking about ways of skipping validation for default values.
I know that I can resolve this problem by simply comparing time in seconds (not ms) but it may cause some (really rare, but nasty) problems if for instance the default second is n and current time has an n+1 second value. be great if there was a way of achieving this by just using mongoose
mongoose mongoose-schema
asked Nov 23 '18 at 17:37
Ivan PIvan P
64821220
add a comment |
I have the following scenario: I need to create a document with a date. The date can be either a future date or a current date that is set by default by my schema. My validation looks like this:
function validateStartDate() {
const { startDate } = this;
return startDate.getTime() >= new Date().getTime();
}
This check fails if the default date is set by mongoose. So, I was thinking about ways of skipping validation for default values.
I know that I can resolve this problem by simply comparing time in seconds (not ms) but it may cause some (really rare, but nasty) problems if for instance the default second is n and current time has an n+1 second value. be great if there was a way of achieving this by just using mongoose
mongoose mongoose-schema
asked Nov 23 '18 at 17:37
Ivan PIvan P
64821220
1
Even if you make this granular to the second it's still prone to errors since you likely have no absolute guarantee of the execution time between when the default is applied and when the validator fires. Also that really should bevalidateStartDate(v)wherevgets passed in as the current value of the assigned path. Derferencing fromthisis also prone to error. This seems to me more like it should be controlled on inputs instead of the Mongoose schema definition, and in which case you simply mark the "schema" as required and let the other logic control such comparisons.
– Neil Lunn
Nov 24 '18 at 2:04
add a comment |
I have the following scenario: I need to create a document with a date. The date can be either a future date or a current date that is set by default by my schema. My validation looks like this:
function validateStartDate() {
const { startDate } = this;
return startDate.getTime() >= new Date().getTime();
}
This check fails if the default date is set by mongoose. So, I was thinking about ways of skipping validation for default values.
I know that I can resolve this problem by simply comparing time in seconds (not ms) but it may cause some (really rare, but nasty) problems if for instance the default second is n and current time has an n+1 second value. be great if there was a way of achieving this by just using mongoose
mongoose mongoose-schema
asked Nov 23 '18 at 17:37
Ivan PIvan P
64821220
I have the following scenario: I need to create a document with a date. The date can be either a future date or a current date that is set by default by my schema. My validation looks like this:
function validateStartDate() {
const { startDate } = this;
return startDate.getTime() >= new Date().getTime();
}
This check fails if the default date is set by mongoose. So, I was thinking about ways of skipping validation for default values.
I know that I can resolve this problem by simply comparing time in seconds (not ms) but it may cause some (really rare, but nasty) problems if for instance the default second is n and current time has an n+1 second value. be great if there was a way of achieving this by just using mongoose
mongoose mongoose-schema
mongoose mongoose-schema
asked Nov 23 '18 at 17:37
Ivan PIvan P
64821220
asked Nov 23 '18 at 17:37
Ivan PIvan P
64821220
edited Nov 23 '18 at 17:42
Ivan P
asked Nov 23 '18 at 17:37
Ivan PIvan P
64821220
asked Nov 23 '18 at 17:37
Ivan PIvan P
64821220
asked Nov 23 '18 at 17:37
Ivan PIvan P
64821220
64821220
1
Even if you make this granular to the second it's still prone to errors since you likely have no absolute guarantee of the execution time between when the default is applied and when the validator fires. Also that really should bevalidateStartDate(v)wherevgets passed in as the current value of the assigned path. Derferencing fromthisis also prone to error. This seems to me more like it should be controlled on inputs instead of the Mongoose schema definition, and in which case you simply mark the "schema" as required and let the other logic control such comparisons.
– Neil Lunn
Nov 24 '18 at 2:04
add a comment |
1
Even if you make this granular to the second it's still prone to errors since you likely have no absolute guarantee of the execution time between when the default is applied and when the validator fires. Also that really should bevalidateStartDate(v)wherevgets passed in as the current value of the assigned path. Derferencing fromthisis also prone to error. This seems to me more like it should be controlled on inputs instead of the Mongoose schema definition, and in which case you simply mark the "schema" as required and let the other logic control such comparisons.
– Neil Lunn
Nov 24 '18 at 2:04
1
1
Even if you make this granular to the second it's still prone to errors since you likely have no absolute guarantee of the execution time between when the default is applied and when the validator fires. Also that really should be
validateStartDate(v) where v gets passed in as the current value of the assigned path. Derferencing from this is also prone to error. This seems to me more like it should be controlled on inputs instead of the Mongoose schema definition, and in which case you simply mark the "schema" as required and let the other logic control such comparisons.– Neil Lunn
Nov 24 '18 at 2:04
Even if you make this granular to the second it's still prone to errors since you likely have no absolute guarantee of the execution time between when the default is applied and when the validator fires. Also that really should be
validateStartDate(v) where v gets passed in as the current value of the assigned path. Derferencing from this is also prone to error. This seems to me more like it should be controlled on inputs instead of the Mongoose schema definition, and in which case you simply mark the "schema" as required and let the other logic control such comparisons.– Neil Lunn
Nov 24 '18 at 2:04
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450948%2fis-it-possible-to-skip-validation-on-a-mongoose-schema-field-if-it-has-a-default%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53450948%2fis-it-possible-to-skip-validation-on-a-mongoose-schema-field-if-it-has-a-default%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Even if you make this granular to the second it's still prone to errors since you likely have no absolute guarantee of the execution time between when the default is applied and when the validator fires. Also that really should be
validateStartDate(v)wherevgets passed in as the current value of the assigned path. Derferencing fromthisis also prone to error. This seems to me more like it should be controlled on inputs instead of the Mongoose schema definition, and in which case you simply mark the "schema" as required and let the other logic control such comparisons.– Neil Lunn
Nov 24 '18 at 2:04