Dustin Long

I'm not really familiar with the proposed `qri workflow` command, as I've been pretty off in the weeds working on other things. My vague understanding is that it's wrapping `save`...

> which could include saving a new transform but would never actually run the transform. This is already possible (on CLI) by running `qri save --no-apply --file transform.star me/my_dataset` >...

> I think it should interact however running qri save --apply currently works. The current behavior is kinda of broken, and we started recommending FSI and transforms not be used...

We should leave this issue open until the problem is fixed in code and isn't possible to hit anymore. Having a work-around is good, but the root problem still exists.

This just came up for me; I am working on a dataset and it would be nice if I could generate an empty meta with all the field names but...

Another possibility, which leaves room for future expansion of this feature: ``` qri get meta --example ``` This reminds me of https://github.com/qri-io/qri/issues/1532, since we're using flags to "imitate" part of...

Using a non-existent reference to mean "the empty dataset" runs into problems. What if we take a cue from languages like go and use `_` to mean that. So `qri...

Sure thing, that's a good suggestion (instead of me just asserting as much and leaving it as an exercise for the reader) Generally, I think there's value in allowing a...

Making this change would also make it easier to implement this suggestion: https://github.com/qri-io/qri/issues/1536.

Figured out the root cause of this bug. The line `workingDataset.body = newBody` does not correctly copy the columns from `newBody` to the `workingDataset` object. Fix should be fairly straight-forward...