-
Notifications
You must be signed in to change notification settings - Fork 825
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ascii art collapsed #6833
Comments
Full width font is often used in Japanese OS and might be in the other multibyte languages as well. We might want to consider to stop using ASCII or having Refs: |
@ginpei thanks for the issue, I marked it as an enhancement. |
By the way, just curious though, I'm wondering how it's supposed to be. Would anyone please share how it look in the western environment? |
It's supposed to say "AMPLIFY FRAMEWORK" like in https://user-images.githubusercontent.com/355808/110403555-20af1f80-8032-11eb-99a8-77d212128b48.png. |
So it just expects wider screen regardless font thing. Thank you so much! |
PR #6497 has been merged to remove the ASCII art and will be part of the next release. |
This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs. Looking for a help forum? We recommend joining the Amplify Community Discord server |
Before opening, please confirm:
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v14.15.1
Amplify CLI Version
4.45.0
What operating system are you using?
Ubuntu 20.04 (WSL2 on Windows10)
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
The ascii art shown when you run just
amplify
is collapsed (see attached image)Expected behavior
The ascii art should look beautiful
Reproduction steps
Run
amplify
without args in CLI.It occurred on VS Code Terminal in default window size with hidden side bar. In my Windows, full-width fonts are used (Japanese)
Log output
Collapsed
Looks good in wider screen
The text was updated successfully, but these errors were encountered: