Matthew Kelly

Interesting! I'll leave this issue open for now, just so I can test the behaviour myself - in case there's something I need to fix 😄

Hi @tinuwalther, I'll have to see how this renders in v1.0.0, and what could be done there. However, in v0.8.3 you can get around this by adding the original missing...

Hi @IvanDrag0, Documentation for this for v1 will exist, as I'm working on making it easier to make custom themes and custom elements. It won't contain anything relating to editing...

Yes, all work for v1 is currently in develop :) I've moved the rendering of elements to javascript, which can be found here https://github.com/Badgerati/Pode.Web/blob/develop/src/Templates/Public/scripts/templates.js I've yet to document how creating...

Interesting 🤔 I've seen this error over in Pode, and it was fixed in the latest version - just need to update Pode.Web accordingly. The error was thrown when other...

Yes, excluding `[System.Management.Automation.PSCmdlet]::OptionalCommonParameters` as well makes sense :)

Accctually, having `WhatIf` could be useful, it might be an idea to leave it out as it is today but have a switch parameter to let the user toggle if...

Change in plan with this one, I've opted to use SSE instead of WebSockets. This means for v1.0 I can enable async processing as the default since SSE works over...

I've also added a `Reset-PodeWebProgress`, which is simply a shorthand for resetting a progress bar back to 0. There's also a new `-AsReference` on `Out-PodeWebElement`, which allows you to create...

Hi @idanmashaal, You're correct, at the moment this isn't supported - at least, without editing the head.pode file any way, but yes this will be lost on an upgrade. I...