Ad
PhpStorm Incorrectly Percieves The Event Constructor To Not To Have Any Arguments
The Event
constructor accepts a typeArg
as its first argument representing the name of the event.
class MyEvent extends Event {
constructor(type, myData) {
super(type); // <-- JetBrains PhpStorm complains: Invalid number of arguments, expected 0
// ^^^^^^
}
}
When invoking the constructor via super()
, JetBrains PhpStorm complains:
Invalid number of arguments, expected 0
While it should expect not only a typeArg
, but there can also be an optional eventInit
! So, why is this and how to resolve the warning?
Ad
Answer
Known issue, WEB-40312 is fixed in upcoming PhpStorm 2020.1
Ad
source: stackoverflow.com
Related Questions
- → How to update data attribute on Ajax complete
- → October CMS - Radio Button Ajax Click Twice in a Row Causes Content to disappear
- → Octobercms Component Unique id (Twig & Javascript)
- → Passing a JS var from AJAX response to Twig
- → Laravel {!! Form::open() !!} doesn't work within AngularJS
- → DropzoneJS & Laravel - Output form validation errors
- → Import statement and Babel
- → Uncaught TypeError: Cannot read property '__SECRET_DOM_DO_NOT_USE_OR_YOU_WILL_BE_FIRED' of undefined
- → React-router: Passing props to children
- → ListView.DataSource looping data for React Native
- → Can't test submit handler in React component
- → React + Flux - How to avoid global variable
- → Webpack, React & Babel, not rendering DOM
Ad