Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ring-apigw-lambda-proxy doesn't play well with compojure.core.routes #11

Open
ricardoekm opened this issue Aug 15, 2017 · 1 comment
Open

Comments

@ricardoekm
Copy link

First of all, awesome idea. Thanks for the lib!

It seems the current version doesn't play well with compojure.core.routes function (to compose routes).

e.g.:
(def handler (routes (-> dont-require-auth-routes (wrap-keyword-params) (wrap-params) (wrap-apigw-lambda-proxy) ) (-> require-auth-routes (wrap-keyword-params) (wrap-params) (wrap-basic-authentication authenticated?) (wrap-apigw-lambda-proxy) ) ) )

If my route is in the first list (dont-require-auth-routes in the example above), the middleware is able to invoke it. Otherwise, it doesn't find the function and returns:

{ "statusCode": null, "headers": null, "body": null }

@philip-healy
Copy link

I'm not seeing any issues with multiple routes. I think you can close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants