Enzzo

I'm implementing this: - Every resolver can declare with keys it consider as a "private key" - before call the parser, I cleanup the query, removing any attempt to use...

Seems that we can export an Apiary blueprint to Swagger (openapi V2) https://help.apiary.io/swagger/ We can first support it by implementing Swagger. With that, we will cover many other user-cases Then...

OpenAPI has the concept of "Security" in paths/routes that we can flow https://swagger.io/specification/

> I think this goes against the goal of what's been introduced with io.pedestal.connector this code was developed before pedestal.connector Websocket may be possible via https://docs.oracle.com/en/java/javase/23/docs/api/java.net.http/java/net/http/WebSocket.html (link to future self)

@hlship I think the basic functionality is working I'd like some feedback from you before continue on other features (I'm planning: SSE and HTTP. `maybe` websockets) Note that the `jdk-httpserver-test`...

I'm implementing `test-request` method and improving the overall structure - making it follow http-kit structure. Soon I will move more code into "root-handler"

Note to future me: https support https://gist.github.com/idurucz/992d95296e39f02646456dc9fc908db8

Also, I'd like a feedback on this: `set-context` behaves in an unexpeted way in "root" context In my mind, it should: `(request/set-context {:uri "/foo/bar"} "/") => {:uri "/foo/bar", :context "/",...

Maybe also add a `:on-finally` or `:always` handler?

I'd add two more features: - Support to delay values (will only start the fetch inside the reg-fx call, as `re-promise` do. - Support literal values ```clojure (rf/reg-fx :promise (fn...