Add ability to override available routes for a <Resource>
#8640
Conversation
This file contains 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
slax57
force-pushed
the
force-resource-routes
branch
from
e0f4bc3
to
3a04b59
Compare
fzaninotto
approved these changes
Feb 10, 2023
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.
Problem
When using
<EditDialog>,<ShowDialog>or<CreateDialog>, these CRUD views are not declared on the<Resource>, and hence theResourceDefinitionwill havehasEdit: false, hasCreate: false, hasShow: false.Thus, any
<ReferenceField>targeting that resource will refuse to render a link, because of those booleans.Solution
Allow to override
hasEdit,hasCreateandhasShowat the<Resource>level.