Fix 500 error on event_type_available_times, user_busy_times endpoints + user busy times component css fix #76
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lgargantini
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix 500 error on
event_type_available_timesanduser_busy_times+ user busy times component fixBE:
event_type_available_timesanduser_busy_timesendpoints are expecting ISO format with 6 milliseconds fragment decimals: e.g.:YYYY-MM-DDTHH:mm:ss.ssssssZ(docs) but current code is usingtoISOString()for date conversion, which by default brings 3 milliseconds fragments decimals (YYYY-MM-DDTHH:mm:ss.sssZ), throwing an 500 validation error.FE: User Busy times component presents an error on the main class:
Before