-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
render_A_Link_Column #412
Comments
I'm not quite sure what your questions is exactly. Seems to be more like a question for help, but this is an issue tracker to report bugs and request features. Please use stackoverflow to ask questions and tag your question with |
That was a feature request, unless it already existed... |
@C-BERBER Can you try to rephrase your feature request? |
Sure Sorry, Feature is to Separate the appearance of the data from the underlying linkage. Either: [Right now the render_COLUMN overrides the base function completely.] Or: Take the link column idea to the entire row (no text) and thus let render_COLUMN do its thing.. End result would be the same. Hope that was a little more clear. |
I've been thinking about this lately: If every column has the ability to become clickable, that could be much clearer than the current set of options. We should think of use cases where the column 'text' already returns a link/button: Wrapping it in |
I'm not sure if I am just not using it properly but my interface is very reliant on taking every value from the table and calling a link to edit said row... The problem is that I am now having to compromise my model to format data that should be done in a presentation layer.
So I guess my ask is this (if it doesn't already exist) have a way for the row to trigger a Link and/or allow the render to render before the link makes it's text entry..
The easier option would be for me to just render the three together from the record into one column link.
Otherwise it is a great package
Thanks
CB
The text was updated successfully, but these errors were encountered: