Richard Ejem
Richard Ejem
> If you are filtering (unlike mapping) you can get less entries, returning `Record` is not safe Yep that is technically true, but Typescript is a compromise between usability and...
Yes it is, but it is a major API change, maybe for Nette 3 one day :) for now, unifying them using interface would be more likely a simple fix...
Another problem - `$control->getOption('type') === 'hidden'` check is done by the renderer. I suggest to make the check using `$control instanceof Nette\Forms\Controls\HiddenField` as it does not make sense to place...
> Pleas look on the tests they are falling on you realization. Thanks for the feedback, but honestly I did this 3 years ago, now I don't even do PHP...
@forivall I don't think that's enough. This is a serious blocker for me and I think possibly for many other developers from using this hook. When one start building more...
@alex-kowalczyk we ended up with writing our own abstraction of React state for complex components, which has a way to get immediate state thanks to internal use of useRef. It...
Yes, thanks for answer, that are possible solutions for me. I just thought this may be useful for others - maybe adding a special event like `zoom-change`, `zoom-manual` or so...
@davidfig today I looked onto this issue again and noticed that you already emit `zoomed` event when it is programmatically changed, namely `type=clamp-zoom` and `type=ensureVisible`. I think if we added...
It is actually broken if you don't render your canvas over whole body and do not supply an InteractionManager from PIXI app. Solution 1: ``` const viewport = new Viewport({...
I didn't mean I prefer it. I just noticed (and prepared a PR with fix) yesterday that the builtin handler is broken under these circumstances (we previously overlooked the insertion...