Cardinal

Hi! Sorry for noticing it only now. Is it still relevant?

Sorry for spamming around, wanted to highlight that it's just another example where more general approach I'm suggesting in https://github.com/danielgtaylor/huma/issues/489 (having already ready and tested code) can help to solve...

@braindev Hi and thanks :) You are right, it's one of the use-cases I created it for. Same as base paths for groups, middlewares are must-have for routing. P.S. It's...

@Jtcruthers that's feasible, but it takes out some of the Huma advantages: declarative routes description. Aside from necessity to duplicate route paths (strictly speaking you should also check HTTP method...

> This is also blocking our adoption of huma, while the hureg by [@cardinalby](https://github.com/cardinalby) looks really nice indeed, we'd prefer for this to be inside huma itself. me too, but...

Don't blame him at all, just addressing comments saying that it should be a part of Huma. As an author of a separate lib I'm ready to deprecate it and...

Hi! It's ok and it's the case for all Github Actions since values are passed to actions using env variables and all are strings

I believe it should be solved in more general way via groups functionality, it's the problem not only with security property but with all the operation properties and transformers (that...

Act is great for testing Workflows. Developing individual actions I also tried to use act, but found that it's better to have integration tests. Especially for JavaScript actions where you...

You can use groups on Huma level instead of defining them on router level. Check out a Huma [registration wrapper](https://github.com/cardinalby/hureg) for that This way you operation will have correct auto-generated...