feat: add renderAsLinkToEntity option to TextField#7490
feat: add renderAsLinkToEntity option to TextField#7490maks-oleksyuk wants to merge 2 commits intoEasyCorp:5.xfrom
renderAsLinkToEntity option to TextField#7490Conversation
|
"This option only has effect on the Is there any specific reason you wont support the |
|
@pfpro the main idea here is to enable displaying text as a link to the detail page. If this display is allowed on the detail page itself, it will be a recursive link, which I don't see the point of |
|
It would be also very nice, if you could set the link to edit action instead of detail. At least, when no detail action is configured. But it would even better, if I could define the link target on my own. |
|
@a-r-m-i-n that sounds good, but it seems to go out of the current scope |
|
You add a function to render a link with a hardcoded target (detail action). If making the target configurable is out of the current scope, the scope is maybe to small 😉 Also, in my opinion the name "renderAsLinkToEntity" is too unspecific. What does "toEntity" mean? How about providing two methods "renderAsLinkToDetailAction" and "renderAsLinkToEditAction". |
|
I think that if we add the ability to configure the target for links right now, it might open up a lot more details that we’ll want to configure—for example, the I also like the suggestion for more specific names, but that might also require more flexible settings |
close #6989