Filatov Dmitry
Filatov Dmitry
Hi, @LexRiver! Could you investigate after which version it appears? Probably it's a bug.
Here's a part of my webpack config for processing tsx files: ```ts { test: /\.tsx$/, use: [ { loader: 'babel-loader', options: { plugins: [['babel-plugin-vidom-jsx', { autoRequire: false }]] } },...
No, it isn't. You need to import `vidom` in tsx files. ```tsx // MyComponent.tsx import * as vidom from 'vidom'; class MyComponent extends vidom.Component { onRender(): vidom.Node { return (...
`setRef` was never be a public api. You can try to use `child.getDomNode()` but I wouldn't recommend using such a way since there's no any guarantee that `this.children` is an...
Sorry for outdated doc ( > child.getDomNode() returns null for me Maybe because you call it before child is rendered to DOM?
Unfortunately there's no any good way to express `defaultAttrs` with TypeScript right now. You can use `this.attrs.value!` to make ts happy.
В какой опере? До хромиума?
Какого поллинга?
Пока ничего определенного не решили. Надо решить что-то с автозаполнением.
If you want to have the same predictable size you'll have to fix it by yourself, for instance in css.