-
Notifications
You must be signed in to change notification settings - Fork 326
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
Allow clickable links in table rows #428
Comments
But if we use that, we couldn't use |
Why not? This proposal would only enhance existing string column capabilities with markdown. If you specify |
One aspect we need to consider before doing this is to make our markdown-to-HTML conversion a bit smarter. It currently wraps all text in |
On second thought, enabling link support via our existing |
Any update on this ? I was making a JIRA issue tracker table using ui.table |
We will try to include it within the next release. |
* rename overlook references to new_tab and url * fix docs example code (showcase) * move LinkTableCellType component to link_table_cell_type.tsx * improve reference to links that include 'http(s)', page -> webpage * improve regex to extract label and link closes #428
* rename overlook references to new_tab and url * fix docs example code (showcase) * move LinkTableCellType component to link_table_cell_type.tsx * improve reference to links that include 'http(s)', page -> webpage * improve regex to extract label and link closes #428
Related #1379 |
via @vopani
Is your feature request related to a problem? Please describe
It helps improving a base UX to render urls directly as links thus making them clickable as opposed to plaintext that user has to manually copy and paste to browser url bar.
Describe the solution you'd like
We have 2 options here:
data_type: 'link'
and render accordingly.TableCellType
-LinkTableCellType
Additional context
We already have a
link
attribute onTableColumnType
that specifies the primary clickable column and might cause confusion so we need to be careful about naming.cc @lo5 @geomodular for discussion
The text was updated successfully, but these errors were encountered: