Open jamesmengo opened 6 months ago
This issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action. → If there's no activity within a week, then a bot will automatically close this. Thanks for helping to improve Shopify's dev tooling and experience.
P.S. You can learn more about why we stale issues here.
still relevant! cc: @karreiro
This issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action. → If there's no activity within a week, then a bot will automatically close this. Thanks for helping to improve Shopify's dev tooling and experience.
P.S. You can learn more about why we stale issues here.
This issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action. → If there's no activity within a week, then a bot will automatically close this. Thanks for helping to improve Shopify's dev tooling and experience.
P.S. You can learn more about why we stale issues here.
This issue seems inactive. If it's still relevant, please add a comment saying so. Otherwise, take no action. → If there's no activity within a week, then a bot will automatically close this. Thanks for helping to improve Shopify's dev tooling and experience.
P.S. You can learn more about why we stale issues here.
What area(s) will this request affect?
Other
What type of change do you want to see?
New feature
Overview
Create a new set of commands that can be used to build and validate platform-owned configuration files such as
.env
,shopify.app.toml
,.shopifyignore
Ideas / Example Commands
.shopifyignore
this could be fed a list of inputs which are matched against the patternsMotivation
Config files are often a set it and forget it kind of thing, so we can forget how painful it can be to get these right.
On top of that, being able to validate your
.shopifyignore
directly against a theme could save valuable feedback cyclesI have a prototype of something along these lines which allows users to validate
.shopifyignore