ENH Do not rely on flush variable #11440
Merged
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.
Issue silverstripe/.github#324
Notes on a couple of places where
$request->getVar('flush')
is used that were not changed:RequestFlushDiscover::lookupRequest() - not changed because it's the central place that checks
$request->getVar('flush')
, somewhere has to do it after allSapphireTest::start() - unlike the new sake, it still uses
CLIRequestBuilder::createFromEnvironment()
which returns anHTTPRequest
. Without significant refactoring it needs to stay this way as you need to be able to use without sake e.g.vendor/bin/phpunit path/to/something