Bartek Jaskulski

@bishopandco I've been stuck with this problem as well. The issue lies in vite's tree-shaking. If your component looks like those presented in `vue-vanilla` package, then vite has trouble to...

Hi @sdirix! I think it more likely Vite issue, as imports from external package are working correctly. I don't event think that DispatchRenderer could work better to somehow inform users...

@NikolayMakhonin Already handled this in #80. Nonetheless, your regex seems less constrained. I would only suggest to write a test for that case.

Anyway, I think this library might need a reliable fork, as @cuth seem not to maintain it for some time

Hi @btxtiger! I think, you need to add following call in your snippet. Without this using `PrettyPageHandler` is ignored in CLI context. See this piece of [source code](https://github.com/filp/whoops/blob/76c1a314f89145de83b5108af4c4695c2d31b352/src/Whoops/Handler/PrettyPageHandler.php#L185-L200). ```php $whoops->handleUnconditionally(true);...

I have played a little with benchmarking, doing 100 sequential requests to each endpoint. I've expected that results would be more consistent, but I'm not sure what is the reason...

@bishopandco following your response on issue eclipsesource/jsonforms#1744 I would like to add example of SFC component with `` for registering renderers. ```vue import type {ControlElement,} from "@jsonforms/core"; import ControlWrapper from...

@bishopandco I do during registration, just like: ```ts { renderer: markRaw(StringControlRenderer), tester: rankWith(1, isStringControl) } ``` For what I know, it doesn't cause any issues about rendering fields.

Thank you @sdirix, it actually does help! I didn't notice that vue-vanilla repository uses renderers in this way in readme section. I think such information could go to some *FAQ*...

FWIW #2759 can _simply_ resolve this issue. Native phpdoc parser interprets `non-empty-string` as ClassTypeNode, but with phpstan parser it is corrected