Kasey

filtering: - what are the things that dirve this functionality, and start from there - we need public/private - currently we use filtering on search and want to use it...

Current consensus is to punt & only allow POST requests w/ application json to use `json.Unmarshall`

Okay so, from what I'm getting, is that our main fields that we need to cover are: `Limit`, `Offset`, `Filter`, & `All` - which are things you do to a...

To narrow this scope, we are only currently using the unsubscribe methods in the automation package. We use `SubscribeTypes` and `SubscribeID` in the automation package, and so need `UnsubscribeTypes` and...

Running into some issues because golang will only compare functions to `nil`, so there is no way to ensure we are removing the correct handler from the list of handlers...

Add `HookSource` interface to `hook` and ensure `workflow.Store` satisfies it ala this comment: https://github.com/qri-io/qri/pull/1797#issuecomment-850549868

To your point about user feedback @Arqu, I'm struggling with how to get this. I think maybe looping @chriswhong into this discussion might be useful. I figured presenting some potential...

> My vague understanding is that it's wrapping save and transforms, and then also adds triggers and completion hooks which are the core of qrimatic. Is that accurate? tbh we...

> which could include saving a new transform but would never actually run the transform. whoa I never even thought of that as a possibility

> Another question (related to FSI being on the back burner), is how workflows interact with working directories. Do you mean specifically allowing users to edit triggers and completors via...