-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Nested date format is different from top level in response #2129
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
Comments
Hello, I see that you've already debugged and found resolution, could you please push a new PR with tests? Thanks! |
Will try later. Also there is another related bug: new object of such Model fails
in my case last_request is null and there is no nested date, didn't dig deep into this,
|
I'm having the same issue, was it merged so far? |
No, that's the reason why this issue is still open. Thanks. |
@divine, question about local tests: readme says that all you need is to run "docker-compose up", Regardless #2129 (comment) - I'm unable to reproduce this for now, will open separate issue if this happens again. Thanks. |
Hello @alexsmko , Yes, you're right indeed, it doesn't start the test. Docker compose file needs to be updated as well, would you like to help? 😉 Thanks! |
This is still an issue:
Any workaround? Sometthing I might be missing? |
Fixed by #3105 |
Steps to reproduce
It looks like $this->serializeDate() should be called in Mongodb/Eloquent/Model.php#L219 in order to mimic Eloquent's addDateAttributesToArray() in Eloquent/Concerns/HasAttributes.php#L168 trait
The text was updated successfully, but these errors were encountered: