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
Support of heterogeneous data types in a given property/column. #315
Comments
Both of your suggestions are definitely coming! To be honest, I'm not super happy with the Link field type at the moment. Since it's two different features however, would you mind extracting one of them into its own issue so that we can track them separately? |
Done! I am not sure of what the best implementation might be, but maybe something like the following:
OR Always support diverse data types in the background, and rather name the data type of columns purely based on their meta-type (multi-select, single-select, formula...), not caring at all whether the elements returned by these meta types are strings, images, links, tags... And the 'status' field of the board views would require the column meta-type to be 'single select', very much like Notion. |
Rather than create a new feature request, I have two use cases for this one:
|
Hi @scottbolte , for these cases you mentioned, you can try |
Thank you @Acylation, Enabling |
What would you like to be added?
In particular, being able to make internal links or images be respectively clickable and visible in Text columns (it works with dataview tables!)
Related but not similar: manually enforce the data type of a given column. For instance, enforcing the conversion of a Links column in a Text column (similarly to what can be done in Notion or even obsidian-database-plugin).
Why is this needed?
Sometimes, a given property can have several data types. For instance, a mixture of internal links, images and text. Currently, when this happens, the column data type falls back to 'Text' and the links become unclickable and the images invisible.
The text was updated successfully, but these errors were encountered: