Feature: Add support for SelectTree without relationship using ->query() #173
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 PR introduces the ability to use the SelectTree component without requiring an Eloquent relationship.
Previously, the component only worked when bound to a model relationship via ->relationship(...). However, there are valid use cases where no relationship exists — for example, when selecting navigation points to insert links inside a RichText editor.
To support this, a new ->query(...) method has been added. This allows developers to provide a custom query directly, enabling the SelectTree component to be used more flexibly across different scenarios.
Key changes:
Example usage:
This enhancement makes SelectTree more versatile and applicable beyond relationship-driven use cases.