Closed deg closed 5 years ago
Thanks for voicing your interest!
In an upcoming version of Vase, we are introducing more control over various aspects of the descriptor itself.
But keep in mind, Vase is only generating routes and interceptor chains -- you can already take full control over the construction of those routes. For example, you might consider post-processing the route sequence generated by vase/routes
-- removing/replacing/short-circuiting the route browser endpoint.
Thanks. Your workaround is easy enough, and solves my problem now.
I appreciate that you will be adding more control in an upcoming version. If adding control of discovery is already in your roadmap, then I'm 100% good here. Thanks!
This is related to #91. The url should be configurable as well.
Currently Vase exposes simple API discovery (
cognitect.vase.routes/describe-api
) as an endpoint at the root of each API tree.This should be configurable, presumably via an option to the API definition in the service
.edn
file since: