Fix: Allow opting out of Caching for environments that don't Support filesystem modifications #27
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.
This pull request updates the caching behavior for class discovery in the framework, making it easier to disable caching in environments that do not support writable file systems. The most important changes clarify and implement a new constant,
TENUP_FRAMEWORK_DISABLE_CACHE, which allows developers to skip caching regardless of environment type. Documentation has also been updated to reflect this new option.Caching logic improvements:
src/ModuleInitialization.phpto support disabling cache whenTENUP_FRAMEWORK_DISABLE_CACHEis set totrue, in addition to skipping cache onVIP_GO_APP_ENVIRONMENT. This makes cache control more flexible for various environments.Documentation updates:
docs/Autoloading.mdto explain that caching is now skipped whenTENUP_FRAMEWORK_DISABLE_CACHEistrue, and provided guidance for using this constant in environments without writable file systems.docs/Modules-and-Initialization.mdto includeTENUP_FRAMEWORK_DISABLE_CACHEas a way to disable caching, along with examples of its usage and explanation of its intended purpose.