block-plus-minus triggers warnings about overwriting block definitions
See original GitHub issueCategory
Plugins
Component block-plus-minus
Describe the bug Warning in console about overwriting existing json definitions.
Block definition #0 in JSON array overwrites prior definition of "lists_create_with".
Block definition #0 in JSON array overwrites prior definition of "procedures_defnoreturn".
Block definition #0 in JSON array overwrites prior definition of "procedures_defreturn".
To Reproduce
Steps to reproduce the behavior:
- Run plugin using
npm run start
- Observe warnings in console.
Expected behavior
No warnings in console.
Additional context
This could be fixed by adding APIs in core to allow for overriding exising block definitions.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Trigger Warnings | Centre for Teaching Excellence
A trigger warning is a statement made prior to sharing potentially disturbing content. That content might include graphic references to topics such as ......
Read more >Trigger and Content Warning Guidance - provost@uconn.edu
Proposed Definition: A trigger warning is a written or oral statement given directly before presenting material commonly known to cause trauma, that discloses ......
Read more >On Trigger Warnings | AAUP
Trigger warnings are a way of displacing the problem, however, locating its solution in the classroom rather than in administrative attention to social ......
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 FreeTop 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
Top GitHub Comments
Thanks @BeksOmega for the explanation. I agree, it would be nice if we can get rid of these warnings some day. For example in my use case, I run unit tests in my continuous deployment process and test my custom blocks and logic. I see dozens of these warnings on every run, which can get frustrating as it makes it hard to see other errors and warnings (if there are any). Here’s a partial screenshot of the continuous deployment output:
Closed by #829