i'm starting to get the impression you can't test your compojure routes from the repl

Maybe https://github.com/ring-clojure/ring-mock can be used

(mock/request :get "/")

I’m not sure I ever tried that. I always have a separate function that implements the route handler and I can easily call and debug that function instead

Thanks I'll think on that. My issue is that it's not clear where in the request response transformation the issue is. It's not in the routing, but the router seems to wrap the middle ware. So I'm not sure how to not include it as the entry point.

I'd use the REPL! Compojure routes can be given the raw request if you ask for it.

(defonce last-req (atom nil))

(defn handle [req]
  (reset! last-req req)
  "Hello, World")

(defroutes app
  (GET "/" req (handle req)))

@U3X7174KS thanks for the suggestion. Do you mind if i share a bit about whats going on here? I'm going to dive into the details and how i'm thinking about them. Its going to be a bit of rant because the issues are only surfaced in real time as i'm trying to debug something. As in, once i know the solution, just plugging it in place isn't really interesting, its how i learned what i had to do and my goal is to improve the process. <rant> I'm trying to use the repl. But it's not clear to me what the best approach is. That is, it's not clear what my easy options are for breaking the problem into small chunks are. To address your comment direclty, i'm not sure the issue is in my handler OR the middleware around it. And trying to get an entry point that walks through both the handle and the middleware is currently a challenge to me and i want to understand both how to solve the problem and why its challenging in the first place. The problem is when we hit the 2022-06-06 endpoint (see below) with a http request the response isn't what we expect. The details are important really. Here are the routes:

(compojure/context
                       "/graphql"
                       _
                       (-> (compojure/routes
                            (compojure/POST "/2022-06-06" _ (request-handler this)))
                           middleware/wrap-keywordize-headers
                           (ring-cors/wrap-cors :access-control-allow-origin [#".*"
                                                                                #"localhost"
                                                                                #".*\.mycentriq\.com"
                                                                                #".*\.centriqhome\.com"]
                                                  :access-control-allow-methods [:post])
                           ring-json/wrap-json-response
                           ring-json/wrap-json-body
                           ring-gzip/wrap-gzip))

(compojure/context
    "/graphql"
    _
    (-> (compojure/routes
          (compojure/POST "/2022-06-06" _ "HELLO WORLD"))
))

(def context
    (compojure/context
      "/graphql"
      _
      (-> (compojure/routes
           (compojure/POST "/2022-06-06" _ "HELLO WORLD")))))

(context <some args here like {:uri graphql/2022-06-06" ...}>)

"Give all routes in the form a common path prefix and set of bindings.

  The following example demonstrates defining two routes with a common
  path prefix ('/user/:id') and a common binding ('id'):

      (context \"/user/:id\" [id]
        (GET \"/profile\" [] ...)
        (GET \"/settings\" [] ...))"

compojure.core/routes [& handlers]

Create a Ring handler by combining several handlers into one.

(myapp {:uri "/" :request-method :post})
; => {:status 200
;     :headers {"Content-Type" "text/html; charset=utf-8}
;     :body "Create Something"}

(def r (compojure/routes
          (compojure/POST "/2022-06-06" _ "HELLO WORLD")))

  (r {})
  ;; => nil

  (r {:uri "/"})
  ;; => nil

  (r {:uri "/2022-06-06" :request-method :post}) => throws exception. hmm may

(require '[compojure.core :refer :all])

  (defroutes myapp
    (GET "/" [] "Show something")
    (POST "/" [] "Create something")
    (PUT "/" [] "Replace something")
    (PATCH "/" [] "Modify Something")
    (DELETE "/" [] "Annihilate something")
    (OPTIONS "/" [] "Appease something")
    (HEAD "/" [] "Preview something"))

  (myapp {:uri "/" :request-method :post})

1. Unhandled java.lang.IllegalArgumentException
   No implementation of method: :route-matches of protocol: #'clout.core/Route
   found for class: clojure.lang.PersistentArrayMap

I feel your pain! I've gotten myself into similar messes myself. To me, it sounds like you're on track digging into what's supposed to happen with your simple example - where you create the simple route table with defroutes. I'd perhaps try: 1. Continuing to dig into the docs - perhaps you'll find that you're having a faulty assumption 2. Perhaps there's some old REPL state sticking around. I'm not in front of a PC right now, so I'm not able to try to reproduce your small example that crashes. I would also expect that example to work.

I tried to reproduce your example, but in my case (with compojure 1.7.0), I'm not getting any errors, it seems to give the expected behavior.

(require '[compojure.core :refer :all])

(defroutes myapp
  (GET "/" [] "Hello World"))

(myapp {:uri "/" :request-method :get})
;; => {:status 200, :headers {"Content-Type" "text/html; charset=utf-8"}, :body "Hello World"}

thats very useful information thanks @U3X7174KS i appreciate you looking into it.

ugh. i still get the exepction with your same setup. wtf could that mean?

;; Connected to nREPL server - 
;; CIDER 1.6.0 (Buenos Aires), nREPL 1.0.0
;; Clojure 1.11.1, Java 17.0.5

double ugh it was clojure enlightment mode

https://github.com/clojure-emacs/cider-nrepl/issues/764 Or at least, thats what i'm seeing. I stand ready to be corrected.

That's what I just wanted to say. I have no problems evaluating the routes themselves. As the defroutes docstring says:

(defmacro defroutes
  "Define a Ring handler function from a sequence of routes. The name may
  optionally be followed by a doc-string and metadata map."
  [name & routes]

(defroutes routes
  (context "/projects" req
    (GET "/" [] (show-projects-page req))
...

(routes (ring.mock.request/request :get "/projects"))

And I have no problems with cider enlighten mode

@U06BE1L6T concerning enlighten mode, if i opened an issue which has a link to a setup project fails for me. You can give it a try if you want to see if it happens for you. https://github.com/clojure-emacs/cider-nrepl/issues/764

Also that mode will often result in highlights which wont go away unless i manually clear them. As in, re-evaling with it turned off doesn't remove the highlights. So for what ever reason, in my setup, it's been a bit of a headache. I get the impression not many people use it, so it might not be getting a lot of feedback from various environments. Do you use an emacs framework like spacemacs or doom by any chance?

I use spacemacs and I do not typically use enlighten mode. I find cider debugger and inspector way more useful and those are my go-to tools.

You could try to debug compojure.core.route-matches to understand what's the difference between the invocations. It seems that it's passing, for some reason, a map while route-matches probably expects something else.