Bug when "created_at" and "updated_at" fields are named differently #736
Conversation
This file contains hidden or 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
When I rename the fields "created_at" and "updated_at" it throws an error when using the getModified() method. It throws the following error: "IlluminateDatabaseEloquentModel::serializeDate():
parallels999
approved these changes
Mar 8, 2023
parallels999
reviewed
Mar 8, 2023
There was a problem hiding this comment.
Closes #735 looks good to me, @anteriovieira can be merged without breaking anything
|
Thanks ❤️ |
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.
When I rename the fields "created_at" and "updated_at" it throws an error when using the getModified() method.
It throws the following error:
"IlluminateDatabaseEloquentModel::serializeDate():