[5.6] Updated mass assignment exception wording#22565
Merged
taylorotwell merged 1 commit intoDec 29, 2017
Merged
Conversation
… key alone is a little vague
GrahamCampbell
changed the title
Contributor
|
Maybe this should be inside the exception class itself? |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Updated mass assignment exception wording for clarity; nominating the key alone is a little vague.
I was finding when running
firstOrCreate()on a model where I neglected to update the$fillablearray was returning an exception with the first key name in it each time. The fix itself was obvious and simple (ie updating$fillable), but I thought adding a couple of breadcrumbs for folks new to Laravel might help.