Repository navigation
refactor: remove legacy foundation components - #85
Merged
Merged
Conversation
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
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.
Summary
Remove the unused resource-bag layer and legacy filtering helpers that no longer participate in Filterable's execution pipeline.
What changed
Resources,FilterableSettings, and all specialized resource bagsgetResources()andsettings()APIs fromFilterableand its facade PHPDocPayloadFactoryandPayloadApplierWhy
These components were remnants of an older architecture. They duplicated state already owned by
Filterable, were not used by the current payload pipeline, and increased the amount of code initialized and maintained without affecting filtering behavior.The active engines continue to read fields, relations, operators, sanitizers, and mappings from their canonical APIs and runtime context.