Don't autoload with class_exists #659
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.
Due to legacy reasons, in my codebase I have all the models being in the root namespace, not in the
\App\Modelsnamespace.When trying to run
php artisan scribe:generate, it would immediately fail when trying to actually load my models (Cannot declare class Account, because the name is already in use, because of the autoloading ofclass_exists. Setting the autoload to false made everything work again.For what it's worth, the parameter it's checking does use Model Binding, so it sounds like it shouldn't be doing this anyway? (
UrlParamsNormalizer::getTypeHintedEloquentModelsfinds it)But either way, thought I'd submit this fix!