-
Notifications
You must be signed in to change notification settings - Fork 15
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
Feature for null start/end dates #16
Comments
Let me see if I understand you correctly, you want to have unset datetime objects before the user selects a date, right? Right now if the date is not set it's 'undefined' by default and shows a placeholder instead. What would be the displayed as a placeholder for a null value? |
oh, sorry, if it's undefined then that should work! I think I missed that. My goal is to let someone say "X starts on 2/2/18 and goes indefinitely". I could just create a button that sets either the start or end to undefined then. |
If i set item.start to a new moment(0), then if I click the undefined item.end date, i get the following error in console:
|
Ahh, interesting... It seems like the start and end dates can not be undefined after all. Would you be able to use start and end datetime as separate directives from the other library or would you prefer adding placeholders and undefined range support here? |
I would highly appreciate such a feature in this one. With two of the other i still would have to encapsulate it to another directive to be have validations and so on. |
Would it be possible to allow for null values for the start and ends dates. Null would indicate indefinite start or end. Kind of like infinity.
The text was updated successfully, but these errors were encountered: