Clear Cloudflare cache if the command exists, otherwise log a warning message. The changes were made to handle the case when the cloudflare-cache:clear command does not exist. #20
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.
Introduces a safeguard for the
cloudflare-cache:clear
command within theCloudflareCacheServiceProvider
. The motivation behind this change is to enhance the robustness of our application by preventing potential errors when the command is not available.Previously, the code attempted to call the
cloudflare-cache:clear
command unconditionally, which could lead to runtime exceptions if the command did not exist. With this update, we first check if the command is registered usingArtisan::all()
. If the command exists, it is executed; otherwise, a warning message is logged.This improvement not only enhances error handling but also provides better visibility into the application's behavior during the boot process. By logging a warning when the command is missing, we can quickly identify configuration issues without causing the application to fail. Overall, this change contributes to a more stable and maintainable codebase.