fix(core): useGetToPath returns undefined
#7163
Merged
+169
−32
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.
PR Checklist
Please check if your PR fulfills the following requirements:
Bugs / Features
What is the current behavior?
useGetToPathreturnsundefinedwhen a partial resource object is passed as parameter. This happens because the hook uses the passed resource directly without looking up the full resource definition from the resources array.What is the new behavior?
The hook now looks up the full resource definition from the resources array using the resource name. This ensures all action routes are available even when a partial resource object is provided.
Also added a warning message when an action route cannot be found.
fixes #7159
Notes for reviewers
Added a new test case to cover the scenario where a partial resource is passed but the full definition should be found from the resources array.