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.
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
feat: Create StartDate and EndDate types [DHIS2-16019] #17454
feat: Create StartDate and EndDate types [DHIS2-16019] #17454
Changes from 6 commits
cd650f1
beb04cf
c0fdefd
3185c25
4937348
9c2bbb8
0d97920
e9c3a7c
097f115
ea4836b
a5ed1d2
11b18b0
b0fedf5
8a3d8dc
927d790
5654ec4
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we leave
startDate=2020-10-10&endDate=2020-10-12 will include anything between 2020-10-10T00:00:00.000 and 2020-10-12T23:59:59.999.
from these docs here as this is at the discretion of the endpoint itself?
Or do we "standardize" on this behavior, in that case it makes sense to keep it here. I am not sure its 100% clear right now with
include anything between
that the endpoints are included as well. So maybe we could change the wording or add(represent a closed interval [startDate, endDate]
.Check notice
Code scanning / CodeQL
Use of default toString() Note test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is enum related code in the
CrudControllerAdvice
. Not sure what it does but I wonder ifCrudControllerAdvice
should stay in here or the code inCrudControllerAdvice
relating enums should be removed if it has no influence. Either way maybe do this in a separate PR.