[SERVER-33578] Add 'onError' option to $dateToString for consistency Created: 01/Mar/18 Updated: 06/Dec/22 Resolved: 16/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
This would never actually be used for anything, but would make the options more consistent with $dateFromString and $convert. |
| Comments |
| Comment by Ian Whalen (Inactive) [ 16/Mar/18 ] |
|
asya closing this based on your final comment. Let us know if we've interpreted it incorrectly. |
| Comment by Asya Kamsky [ 15/Mar/18 ] |
|
Since there cannot be an error converting a valid date to a string, I'm not sure that adding "onError" is useful unless it will be used when the "date" input is not a valid date - and my understanding is that we would still throw an error in that case. Having "onError" that isn't used on any errors that can actually happen feels wrong to me. |