Closed mih closed 1 year ago
So maybe this can be supported as a sideffect of #19?
For every TSV sheet, we could have a JSON file (same name, different extension). For a single
sheet this would be an object (any content). If it exists, it is loaded first, and the TSV content overrides its content (if it conflicts for any keys). This makes it possible to inject @tabby-...
statements. If a corresponding TSV does not exist (but the JSON does), the JSON would be used as-is (and is than subject to contextification and overrides) -- essentially being a JSON-only tabby
(fixed #19).
For many
sheets we have two scenarios:
@tabby..
imports
This is presently not possible. I have a test that confirms it.
However, this is an essential feature, because it allows for completely hiding away the sheet-linkage from a person that only works with the tabular components.