Futures

Now that the event run urls can have a pretty long list of query parameters attached, it would be nice to be able to quickly share just the url path without the parameters.

I would really like to be able to specify delays in smaller time units than minutes. I have an automation that has to wait for an order to finish processing before it runs, but I need it to run soon so that the customer can see certain stuff on their account page after placing their order. 1 minute can be a really long time for the customer to wait for this to appear on their account page when they're waiting for confirmation that their order has been processed. Even if we can get delays in units of 10 seconds, that would be much better.

Google's APIs require OAuth, which isn't really a feasible thing for the "http" action. Let's figure out how to do this properly.

It would be nice if cancelling child events would be possible. :)

See thread here - https://usemechanic.slack.com/archives/CURE65U2W/p1621029857260600 - where integer keys are shifting while editing

If user is editing the task, it would be great if they could press CMD+S (or CTRL+S) to save the task, instead of getting the native OS "save this webpage" dialog).

Just some thoughts on how to improve the web-based editor in Shopify. • I've seen this post: https://mechanic.canny.io/futures/p/improved-code-editor – but it wasn't clear if it applies to the web-based editor in Shopify • I'm also aware of the VS Code extension for Mechanic Liquid: https://marketplace.visualstudio.com/items?itemName=timdmackey.mechanic-liquid – That doesn't apply here because I am talking about the web-based editor in Shopify So here it goes: Dark theme (nice to have) A better light theme, specifically around comments (comments are highlighted like anything else right now) VSCode / Sublime style auto-complete that suggests keywords like variables Feel free to close if I've just missed this somewhere!

It's very ugly to keep writing {% ... %} on every line. Allowing the "liquid" tag gives the ability to write cleaner code (at least where using "liquid" tag is possible). Note that it's not always possible to use "liquid" tag. In some situations, it can be used together with "echo" tag, as described here: https://adtc.github.io/liquid/tags/template/#liquid

Original title: First class tag support for graphql mutations Would love to be able to just get the result of a graphql mutation in the same manner as a graphql query, without having to check and filter perform actions. If that isn't viable due to platform/API restrictions, then how about the ability to wrap a custom user event around a mutation, and then being able to just listen for the custom event to get the mutation result?

It would be helpful to have the option to get notified in the event of a task or event failure. Ideally email or text,