Best way to handle warning on overriding existing format
See original GitHub issueWe have a custom implementation for handling video, in which we extend BlockEmbed
and provide a custom implementation, which is then registered for “formats/video”. This results in a warning being printed to the console.
Steps for Reproduction
- Define a new blot-implementation for, for example, video
- Register blot with Quill using Quill.register
- Open console
Expected behavior: To not see a warning from Quill about overriding a format
Actual behavior: A warning, see below, is printed.
Platforms:
Latest stable Chrome and Safari.
Version: 1.3.6
Issue Analytics
- State:
- Created 4 years ago
- Reactions:9
- Comments:7
Top Results From Across the Web
How to hide "Is this intentional?" warning in Ext JS 6?
You can easily override the warning by forcing the "update" parameter to be set to true when addAlias ...
Read more >How to override the Alert Name and Alert Description of a ...
First, we need to create an Alert String Resource, and a typical DisplayString for our Override for name and description. You can make...
Read more >C# Compiler Options - errors and warnings - Microsoft Learn
The following options control how the compiler reports errors and warnings. The new MSBuild syntax is shown in Bold.
Read more >warnings — Warning control — Python 3.11.1 documentation
The printing of warning messages is done by calling showwarning() , which may be overridden; the default implementation of this function formats the...
Read more >Warning Options (Using the GNU Compiler Collection (GCC))
The specifier for a warning is appended; for example -Werror=switch turns the warnings controlled by -Wswitch into errors. This switch takes a negative...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
One fix we discovered for this was to change the Quill debug setting:
Quill.debug('error')
Changing the level to
error
will suppress warnings like this one.Quill.register method provide a “suppressWarning” argument. It works !