Improve DX when missing filter class import #3307
Closed
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
|
I see, I agree that the message is clearer. I'd be 👍 to merge this as a new feature, may you check why the tests are failing though? |
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.
Improve DX to get more helpful message when missing import for filter class.
Currently we get:
The filter class "SearchFilter" does not implement "ApiPlatform\Core\Api\FilterInterface". Did you forget a use statement?After this we'd get:
The filter class "SearchFilter" does not implement "ApiPlatform\Core\Api\FilterInterface" in "ApiPlatform\Core\Tests\Fixtures\DummyEntityInvalidFilter". Did you forget a use statement?But this changes behavior a little bit, because now when constructing ApiFilter annotation with invalid class it won't throw directly.