(BSR)[API] fix: check order of start and end dates when editing colle… #16314
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.
…ctive stock
But de la pull request
Ticket Jira (ou description si BSR) :
Ajout d'un check sur l'ordre start < end quand on édite un collective stock, comme cela a été ajouté récemment côté api publique
Actuellement la route peut recevoir
endDatetime
seul avec une date qui précèdestock.startDatetime
. En pratique on évite le problème actuellement car on reçoit toutes les dates du front (?)Si on reçoit
startDatetime
seul, on a une logique endDatetime = (startDatetime reçu) donc on n'avait pas le soucis dans ce cas làVérifications