Loss of data for datetime fields if using a getter/setter #44
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.
Following #39 , support for multiple datetime deserialization formats was added, but there is a bug where if the field requires a setter, the temporary variable made to hold the DateTime object has the same name as the temporary that will be passed to the setter.
I've used the same script as in that PR, and fixed the mistake where
start_date
andend_date
of the test data array were written in camelCase instead of snake_case. The issue appears when theCourse::startDate
orCourse::endDate
fields are set to private instead of public. the{{ date }}
variable is the same as the{{ modelPath }}
, and is unset by the end of the sectionP.S.: First time I've made a PR with the tests first 🥳 but it's due to my own mistake😞