Voltra comments

Results 68 comments of


                                            Voltra

Doesn't compile using mingw64 on Windows

Sadly no, I'd have to dive into how to parse `__PRETTY_FUNCTION__` and add that to the lib

Add proposal for template renderer

Something I don't think I've seen in the discussion yet: we don't *have* to change all the libraries' and frameworks' rendering engines, they can just provide (façade?) adapters that satisfy...

More control over which favicons are generated

see #312

DataTable lazy loading paginator bug

I think I might look into it this week-end and make a PR, but I might just end up replacing `:first="lazy ? 0 : d_first"` with `:first="d_first"` (I'm still unclear...

Unable to add items

I noticed that `HandlesNavigationBuilder` uses a `mountedActionData` property where `InteractsWithActions` exposes a `mountedActionsData` property. Would that be the cause of the conflict? Is it a syncing conflict?

[BUG] ```npm run / start / test``` cannot find module when path to directory contains ampersand ```&``` or caret ```^```.

Same here with NPM v9.6.3 on a Node v14.21.3

[BUG] ```npm run / start / test``` cannot find module when path to directory contains ampersand ```&``` or caret ```^```.

What constitutes a valid pathname is not up for debate. Systems allow names such as `R&D`, therefore they should be handled properly by libraries. Any path/fs library worth being used...

[BUG] ```npm run / start / test``` cannot find module when path to directory contains ampersand ```&``` or caret ```^```.

I'll try to have a look if I can find a way to fix the paths handling (in npm or node's module resolution directly)

[BUG] ```npm run / start / test``` cannot find module when path to directory contains ampersand ```&``` or caret ```^```.

It looks to me like that the issue might come from `promise-spawn`'s path handling on Windows, quite likely [this part](https://github.com/npm/promise-spawn/blob/16b36410f9b721dbe190141136432a418869734f/lib/index.js#L86C1-L98C6)

Add option to control whether disable Escape to close modal

Strongly interested in this option too (and all the other options we could have)