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
When you run one of the new commands, it wipes out the shell output that is currently visible in the terminal window. It removes not only the Storyblok command that I have just typed, but also output of my previous commands that have nothing to do with the Storyblok CLI.
To present this, I set up this scenario where I typed echo n ten times, from 1 to 10. I resized the window so that the numbers 1 and 2 aren't visible. Then, I run a pull components command. Here are the results:
Terminal window before
Terminal window after
(PS: I can also share a video privately because it includes my space id and I don't know how to censor a video)
Expected behavior
I would expect that my shell output is not deleted. I also expect to see the Storyblok command that I ran in the output.
Relevant code
I'm not sure if this is relevant, but this is the way I run the CLI right now from the next branch:
This bug is regarding the
next
branch.Current behavior
When you run one of the new commands, it wipes out the shell output that is currently visible in the terminal window. It removes not only the Storyblok command that I have just typed, but also output of my previous commands that have nothing to do with the Storyblok CLI.
To present this, I set up this scenario where I typed
echo n
ten times, from 1 to 10. I resized the window so that the numbers 1 and 2 aren't visible. Then, I run a pull components command. Here are the results:Terminal window before
Terminal window after
(PS: I can also share a video privately because it includes my space id and I don't know how to censor a video)
Expected behavior
I would expect that my shell output is not deleted. I also expect to see the Storyblok command that I ran in the output.
Relevant code
I'm not sure if this is relevant, but this is the way I run the CLI right now from the
next
branch:I created a fork where I committed in the
dist
directory so that it's possible to install it as a npm dependency straight from the github repo.The text was updated successfully, but these errors were encountered: