Do not use request if no request validation set #207
Merged
Conversation
This file contains 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
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.
WHY
fixes: Laravel-Backpack/community-forum#1191
BEFORE - What was wrong? What was happening before this PR?
When choosing
arrayorfieldvalidation for a crud-controller, theuse Requeststatement would still be in the generated class, raising errors as that class is only created when usingrequestvalidation.AFTER - What is happening after this PR?
We do not use the request if the validation does not use the request.
HOW
How did you achieve that, in technical terms?
replaced some strings in the stub.
Is it a breaking change or non-breaking change?
non