lonix1

Straight from the horse's mouth... should be good. I'll look into it, thanks.

One needs to ensure the script only loads once. [Here](https://stackoverflow.com/a/74426379/9971404) is the solution.

Okay figured it out... ```` "command": "gnome-terminal --working-directory=/foo/bar/baz command arg1 arg2", ```` What we need is a macro like `${projectdir}` that resolves to the project's root. So we can use...

Okay figured it out... ```` "command": "gnome-terminal --working-directory=`pwd`/foo/bar --command 'command arg1 arg2'" ```` Though this could be made simpler.

This also happens when debugging extensions.

Thanks! > capture fields' initial value so we can defer validation until that value has changed Yes I did something similar - I saved the initial value to a data...

The original plugin's behaviour is to validate on blur, so that should be the default given that this library is intended to be a drop-in replacement. That said, I suspect...

I didn't realise you put it behind a new option, in which case it's all good. I suppose Keith / Phil should decide on the rest. At some point we...

I'm increasingly finding the original default (validate on input/change or blur) is aggravating, and that many (/most?) modern sites don't tell you a field is invalid until you actually try...

Is this feature dependent on first handling all [these](https://github.com/dotnet/efcore/issues/30173) issues?