Jacob Hauberg Hansen
Jacob Hauberg Hansen
Cases for conditions relating to assets or resources may be ambiguous due to lack of information. For example, take the scenario below, where a project has several targets, each with...
Or could it be just another datasource (that somehow doesn't trigger card generation; probably just from lack of `@template` columns)? Then a user could potentially have plenty of these "shared"...
The point at which Markdown formatting is applied should probably be *before* resolving fields. For example, I just encountered this situation: **shared.csv** ``` @definition,@value "token","*" ``` and then a datasource...
In the example below, one datasource without backs (`instants`) is combined with another datasource (`references`) that *do* have backs- this cause the backs to not be properly aligned (they should...
Take a Magic: the Gathering card and you'll see a range of icons on the top-right. How would we specify such an element from a datasource?  There's at least...
In theory, I think all definitions could actually just be resolved right away instead of *on-demand*. The data is immutable during building anyway- so why resolve the same things over...
I find that the hardest part about making a template is taking the first step. Maybe the project could come with a set of pre-defined, typical-looking, templates ready for use?...
Currently, it's not possible to specify a custom card size. It has to be one of the pre-defined sizes. This makes sense, because some variables must be manually set; i.e....
Auto-layout could be a very powerful feature if it actually created "layouts". Currently it just determines what each field and _might_ be, then lays them out vertically. This is useful,...
Currently, it's a relatively deep loop with lots of things going on. Some of these things that happen are also pretty similar. I think it could do with a good...