-
-
Notifications
You must be signed in to change notification settings - Fork 802
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
fix[ux]: empty hint #4351
base: master
Are you sure you want to change the base?
fix[ux]: empty hint #4351
Conversation
|
It seems like a code smell that we are creating empty string hints in the first place. Do we know where they are coming from? |
I think its as in this - #4351 (comment) - just the |
note the regression comes from #4154 -- the previous code checked for truthy value of |
Yeah, I think there are two main solutions:
I think the second solution is cleaner, but the first solution ensures that we catch any missed empty string hints. |
i think 2. is better -- we should not be supplying empty string as a hint! |
Hope its better now :) |
What I did
Remove empty hint message from exceptions. As in #4313.
How I did it
Modify the check of absent hint to include an empty string.
How to verify it
Commit message
Commit message for the final, squashed PR. (Optional, but reviewers will appreciate it! Please see our commit message style guide for what we would ideally like to see in a commit message.)
Description for the changelog
Cute Animal Picture