You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a thought that it would be good, if possible, to have a solution such as having a development sales channel that could be used with the CLI/theme development to test products and features beyond the PDP.
I've no doubt there are many technical implications and possible restrictions, so perhaps there's a much better way of achieving this.
Motivation
I was testing a feature that required me to know what template a product was using within the cart, but the product was new and not ready for publishing and as such set as a draft.
I thought it would be great to not have to do the mad sprint to mark as hidden from SEO via metafields, publish, test, unpublish, remove metafield flag as this is all so laborious and prone to human error.
The text was updated successfully, but these errors were encountered:
What area(s) will this request affect?
Theme, Running your code locally
What type of change do you want to see?
New feature
Overview
I had a thought that it would be good, if possible, to have a solution such as having a development sales channel that could be used with the CLI/theme development to test products and features beyond the PDP.
I've no doubt there are many technical implications and possible restrictions, so perhaps there's a much better way of achieving this.
Motivation
I was testing a feature that required me to know what template a product was using within the cart, but the product was new and not ready for publishing and as such set as a draft.
I thought it would be great to not have to do the mad sprint to mark as hidden from SEO via metafields, publish, test, unpublish, remove metafield flag as this is all so laborious and prone to human error.
The text was updated successfully, but these errors were encountered: