hi, hoping someone might be able give me some pointers I am having issues with an exception but I have no traceback

"class": "java.lang.Exception"

I have these middlewares enabled swagger/swagger-feature parameters/parameters-middleware muuntaja/format-negotiate-middleware muuntaja/format-response-middleware exception/exception-middleware muuntaja/format-request-middleware coercion/coerce-response-middleware coercion/coerce-request-middleware

iirc, I think you can get the full stack trace if you disable (un-comment) exception/exception-middleware

I do have that middleware enabled above

but it fails to give a full stack trace, I have figured out the issue now, basically database was not setup when run through the api

but I would love a way to get a full trace, seems this sort of error would have been easy to spot if it had not been hidden

"disable" ☝️ 🙂

oh so comment out the exception middleware

yes

I think I overrode the exception middleware (wrote my own) that wraps the original and logs the exception (available stacktrace). could also just print it, depends what you want.

oh yeah that works, seems counter intuitive would expect it to catch the full exception and return

that's helpful anyway thanks for that spent so much time trying to diagnose that

Another question 🙂 any way to convert this format from honeysql to a json string :release_date #clj-time/date-time "2019-04-30T23:00:00.000Z" currently muuntaja is coercing it into its parts like below. "release_date": { "year": 2019, "dayOfMonth": 30, "dayOfYear": 120, "dayOfWeek": 2, "era": 1,

I have been looking into coercision via spec tools but finding it difficult to work with, figure this is a common requirement so likely an easier way ?

@oliver.marks check the last example here, about adding JodaTime support to Jsonista: https://github.com/metosin/jsonista#examples (and check Muuntaja/Reitit docs about adding those Jsonista options)

okay thanks will see if i can figure out how to add that 🙂

not having much luck with jsonista, perhaps i am confused. I have created a new muuntaja instance with (assoc-in [:formats "application/json" :encoder-opts :date-format] "yyyy-MM-dd")))) but it does not change the format

the link has you creating a mapper do you need to inject that mapper into the encoder-opts in some way

dont suppose there is a working example around some where ?

taking it to a much simpler example this is what I am testing with. (def new-muuntaja-instance (m/create (-> m/default-options (assoc-in [:formats "application/json" :encoder-opts :date-format] "yyyy-MM-dd")))) (->> {:test (LocalDate. 0)} (m/encode new-muuntaja-instance "application/json" ) (m/decode new-muuntaja-instance "application/json" ))

Is it possible with client side reitit to use both fragment routes and non-fragment routes simultaneously?

got a step further seems its because the database is returning dates in joda time and the example uses (java.util.Date.)

so the date formatting is not applied not sure how to correct that

finally figured it out, needed to pass :module to the encoder-opts :)