David Luzar
David Luzar
Looking at the source code, there's not much to be broken here. It seems somewhere along to way the `eslint-plugin-rulesdir` plugin is re-required. Not sure by whom. Could this be...
I've run a search across my whole drive and there's only a single `eslint-plugin-rulesdir` package, so the issue must be in how vscode/eslint handles it. Either way, thanks for the...
Meanwhile, if this helps someone: `[email protected]` is the last version that doesn't show pop-ups for me on win7, `fork` mode (above that, it doesn't matter if I run `fork` mode...
Still issues on `[email protected]` win7, config: ``` "exec_mode": "fork_mode", "instances": 1 ```
@JoviDeCroock what does React do in this case? Binds `keydown` event and prevents it, whenever an input is controlled (there's `value={value}` on it)? Can't Preact do the same?
Right. Preventing `keydown` wouldn't actually help because `e.target.value` couldn't be used anymore and you'd need to set up workarounds around `e.which` and that opens a whole new can of worms...
@JoviDeCroock he's right --- in his example it should prevent writing numbers which it fails to do so due to this bug. `maxLength` doesn't have a say in this. Similarly,...
@Crysp it seems the only workaround is to leverage the behavior that `useState` does shallow comparison, and use a non-primitive to force re-render: ```js const ControlledInput = () => {...
Hmph.. checking CM spec, it probably should behave like this: ``` 0 - foo 1 2 - bar 3 4 5 - baz ``` should result in `[0,2]` and `[2,5]`...