fix(core): work around Pest test file autoloading#1895
Merged
Conversation
brendt
approved these changes
Feb 12, 2026
Member
brendt
left a comment
brendt
left a comment
There was a problem hiding this comment.
Weird error, but this seems like a good workaround. I'm fine merging this
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
2 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.
Closes #1894
During discovery,
class_exists($className)will throw if$classNamepoints to a Pest test file. The exception is an assertion error in Pest's backtrace, I'm not sure why exactly it happens.I figured catching the assertion error here would be good enough a work around, but it would be nice if you could take a proper look at it @brendt