-
Notifications
You must be signed in to change notification settings - Fork 553
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Output warning instead of raising an exepection on default type mismatch
See #435 (comment) Closes #533.
- Loading branch information
Showing
2 changed files
with
5 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
605897b
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.
Even a warning seems quite disruptive here 😕
The problem, IMO, is that the warning appears directly inside the user-facing UI, because of what this library is used for:
It's complaining to someone who can't fix it, and likely doesn't even know what it's talking about.
Perhaps it could go back to raising, but only when a (default off, for compatibility) config setting is enabled?
That way developers can enable it, gain the safety, and fix their code, without immediately disrupting the workflow of their downstream users.