You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an option to have one key with a list of values. That can be chosen per column. You'd get the array for dataview. Maybe readability isn't that great, but I don't think having multiple times the same key is a good idea. In normal YAML it would only recognise the last key in that case.
For dv inline YAML it may work, but I'm probably not going to support that.
There is an option to have one key with a list of values
What option are you mentioning? (I hope that I don't miss anything you have already said this time)
but I'm probably not going to support that
I understand and agree with you. I suppose with regex this can be a quick fix. I'm just wonder: assuming that you don't have to spend effort to make this works, but only need to add features based on their usefulness, how do you decide if a feature should be added or not?
For every column it asks whether the values in the cell should be separately formatted and you can choose the delimiter for splitting them. But then it will have these multiple values associated with one key, not multiple times the same key.
how do you decide if a feature should be added or not?
It's based on whether I'd use it myself. This script only exists because I had written a custom script for someone, and decided to make a general-purpose script for others to profit as well. I don't use the script myself.
And regarding usefulness: the result is the same (different values broken up in a cell), just the way it is done is different. So this is just cosmetic :)
This is useful in Dataview queries, since with
you get a string, while with
you get a list
["foo","bar"]
. This would also be easier to read, if the value is sentence-longThe text was updated successfully, but these errors were encountered: