Futures

It would be great to have some kind of code snippets folder that can be shared between tasks so that I don't need to do a lot of copy-pasta and can do something like: {% func 'add-product-tags', product: product %} or {% include 'add-product-tags', product: product %} or any other syntax

Liquid is pretty chill about invalid syntax, as was the spirit of earlier internets. :) The following sample doesn't raise an error, but also just doesn't work as written - it just returns true every time. {% if event.created_at | date: "%s" > 1727886979 %} Consider either raising an error or displaying some kind of warning in cases like this.

A message doesn't have to be a string. A message could be another kind of object. This future is about transparently passing error messages around without coercing them strings every time. In this future, when given an error object {% error foo: "bar" %} , the resulting mechanic/errors/task event renders {{ error.message.foo }} as bar . https://usemechanic.slack.com/archives/CURE65U2W/p1728580019668949

Shopify's webhook API has the ability to include metafields if the webhook is created using the metafield_namespace property. It would be really useful if Mechanic gave us the option to specify a list of metafield namespaces to include on different Shopify events. The benefits are: Programmers could skip making an API call to shopify when metafields are needed, resulting in less complex coding. Removing the need for an API call would lessen the impact on Mechanic's overall API quota for a shop. References: Webhook documentation Further Slack Discussion

To enable variable interpolation as well as using liquid filters within a string. Helps with templating, especially if storing liquid code as task options. See this thread for more information: https://usemechanic.slack.com/archives/CURE65U2W/p1725391368524659

A task's version history page runs the risk of timeouts when displaying hundreds of versions. This could be better. :)

This would make it easier for folks to notice when a Shopify Liquid filter doesn't have support in Mechanic Liquid. https://usemechanic.slack.com/archives/C070Q3SDKD1/p1714325458749889

Similar to the metafield_tag Liquid filter. This would allow rich text metafield output to be used in email notification tasks, among other things. https://shopify.dev/docs/api/liquid/filters/metafield_tag

Right now you have to click "Go Live" to see new events, but that removes all the filters you have set, so you have to click the back button afterwards to get back to the filtered view. Alternatively, have the "Go Live" button to preserve the filtered view and use a different button to clear all filters at once (and go live).