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
🅰 : We continue to support $SHOPIFY_API_KEY, but stop logging a deprecation warning when we get the key from there rather than --api-key directly.
🅱 : We also deprecate $SHOPIFY_API_KEY in favour of $SHOPIFY_CLIENT_ID and clarify deprecation warning.
Tip
The flags config implies it will automatically check $SHOPIFY_FLAG_APP_API_KEY/$SHOPIFY_FLAG_CLIENT_ID environment variables, if --api-key/--client-id are omitted. Maybe we should use those? Although for some reason, we have both those flags as hidden.
The text was updated successfully, but these errors were encountered:
Problem
We are triggering our own deprecation warning.
--api-key
has been renamed to--client-id
--api-key
is not provided, we check for$SHOPIFY_API_KEY
, and set it as--api-key
--api-key
is set, we emit a deprecation warningcli/packages/app/src/cli/commands/app/dev.ts
Lines 144 to 151 in 2450a80
Solution
$SHOPIFY_API_KEY
, but stop logging a deprecation warning when we get the key from there rather than--api-key
directly.$SHOPIFY_API_KEY
in favour of$SHOPIFY_CLIENT_ID
and clarify deprecation warning.Tip
The flags config implies it will automatically check
$SHOPIFY_FLAG_APP_API_KEY
/$SHOPIFY_FLAG_CLIENT_ID
environment variables, if--api-key
/--client-id
are omitted. Maybe we should use those? Although for some reason, we have both those flags as hidden.The text was updated successfully, but these errors were encountered: