It appears to me that when using the CLI to locally develop a theme, you cannot log in as a storefront user - the auth redirects back to the live site. This requires that any code changes get pushed and tested through the store and the theme editor / preview which is quite inefficient.
For building and testing theme features centered around a logged-in user experience, the CLI theme host needs to support local login
Motivation
Building customer-facing pages with specific pricing, order history, etc. This is not for an app - we are building these capabilities natively into our theme for speed and to reflect very exact, unique use cases in our product configuration that are not efficiently or easily deal with in other apps.
What type of project(s) will this request affect?
theme
What type of change do you want to see?
New feature
Overview
It appears to me that when using the CLI to locally develop a theme, you cannot log in as a storefront user - the auth redirects back to the live site. This requires that any code changes get pushed and tested through the store and the theme editor / preview which is quite inefficient.
For building and testing theme features centered around a logged-in user experience, the CLI theme host needs to support local login
Motivation
Building customer-facing pages with specific pricing, order history, etc. This is not for an app - we are building these capabilities natively into our theme for speed and to reflect very exact, unique use cases in our product configuration that are not efficiently or easily deal with in other apps.