zetti-caletti

> This feature should return a url like > > /getUsers?randomParam=randomValue > > Or return the app base url too? Because if needs the base url I think can be...

@micalevisk @ologbonowiwi @kamilmysliwiec I forked the project, created a branch and added the feature with my ideas. It was hard but I liked it because I never saw the internals...

Ok, how to extend the HTTP adapter? But why don't you make this part of the framework? If YOU have to write for example a rest api, how would you...

> as the http adapter is a concrete JS class (namely `ExpressAdapter` and `FastifyAdapter`). You could extend it like any other class and pass it to the `NestFactory.create` > >...

> > You can also do a PR, maybe your solutions gets accepted and integrated in the framework :) > > Sure! I didn't have time to try that out...

The method could also accept both solutions: whether controller and method or route name. But in my opinion the solution with route names has the advantage that you don't have...

> unless I'm missing some edge case, my requirements for such are pretty much in that sample snippet I've made: > > ```ts > interface GenerateUrlOpts { > controller: Type,...

> unless I'm missing some edge case, my requirements for such are pretty much in that sample snippet I've made: > > ```ts > interface GenerateUrlOpts { > controller: /**...

> in my proposal, you could only generate URLs if your app has the access to the controller. So what's the use case of using the hostname other than the...

> IIRC most url generators have a separate param to generate absolute vs relative urls. If one is generating urls for cli apps or sending emails, then one probably want...