-
Notifications
You must be signed in to change notification settings - Fork 72
chore: Add migration warning #1477
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
Conversation
| borderStyle: 'round', | ||
| }; | ||
|
|
||
| export async function logInBox({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I figured it made sense to make a wrapper around this so we don't need to repeat the same options and dynamic import in multiple places.
kemmerle
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks clean, and I like the warning design! ![]()
lib/ui/boxen.ts
Outdated
| export async function logInBox({ | ||
| contents, | ||
| options, | ||
| fallBackToNoBox = false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I love this variable name lol, but I'd also be fine with removing it and always falling back to no box. Or defaulting to true. We should probably be falling back to no box in the fire alarm middleware too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha, I had such a hard time naming it. I'll make it fallback by default and remove this. I think it makes sense that we would probably want to have a fallback in place at all times.
Description and Context
Add a more explicit migration warning for projects: