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
Describe the bug
Hi,
Exist a bug on themekit version 1.1.3, on theme get --list . Now theme_id is mandatory all times, this not works because --list serve to find the theme_ids o the first place.
I find a bypass using theme get --list -p=[your-api-password] -s=[your-store.myshopify.com] -t=0
To Reproduce
Steps to reproduce the behavior:
run command 'theme get --list -p=[your-api-password] -s=[your-store.myshopify.com] '
you'll receive the error invalid environment [development]: (missing theme_id)
Expected behavior
use the command 'theme get --list -p=[your-api-password] -s=[your-store.myshopify.com] ' without the need to add a fake theme_id
Environment (please complete the following information):
OS [e.g. iOS]: windows
Themekit version (run theme version to check): 1.1.3
Editor [e.g. atom, sublime]: vscode
Ignore:
Additional context
I just update to 1.1.3, the application shows a msg about the update but here i can't see the release 1.1.3, the last release when i write this is 1.1.2.
The text was updated successfully, but these errors were encountered:
Describe the bug
Hi,
Exist a bug on themekit version 1.1.3, on
theme get --list
. Now theme_id is mandatory all times, this not works because --list serve to find the theme_ids o the first place.I find a bypass using
theme get --list -p=[your-api-password] -s=[your-store.myshopify.com] -t=0
To Reproduce
Steps to reproduce the behavior:
invalid environment [development]: (missing theme_id)
Expected behavior
use the command 'theme get --list -p=[your-api-password] -s=[your-store.myshopify.com] ' without the need to add a fake theme_id
Environment (please complete the following information):
Additional context
I just update to 1.1.3, the application shows a msg about the update but here i can't see the release 1.1.3, the last release when i write this is 1.1.2.
The text was updated successfully, but these errors were encountered: