Skip to content
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

[5.4] Null Morph Map ErrorException #18921

Merged
merged 2 commits into from
Apr 24, 2017
Merged

[5.4] Null Morph Map ErrorException #18921

merged 2 commits into from
Apr 24, 2017

Conversation

ConnorVG
Copy link
Contributor

@ConnorVG ConnorVG commented Apr 24, 2017

Currently, if you call getActualClassNameForMorph without the morph map set, it will throw an error because Relation::morphMap() returns null instead of (what I would expect) [].

Is this expected behaviour? If so, why is this expected behaviour?

ConnorVG and others added 2 commits April 24, 2017 16:54
Currently, if you call `getActualClassNameForMorph` without the morph map set, it will through an error because `Relation::morphMap()` returns `null` instead of (what I would expect) `[]`.

Is this expected behaviour? If so, why is this expected behaviour?
@taylorotwell taylorotwell merged commit ab05609 into laravel:5.4 Apr 24, 2017
@ConnorVG ConnorVG deleted the patch-1 branch April 25, 2017 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants