Devlog
The Content-Type problem is SOLVED……
What was the problem? (My reading skills? ) there are two headers with application/json:
-
Content-Type(POST) -
Accept(GET)
TheAcceptheader isn’t required ( can be*/*,application/*orapplication/json).
So theContent-Typemystery is mostly FIXED but I still need to check with a real Volvo car ifContent-Typeis actually required. (I’ll do it tomorrow.)
Changes:
-
Acceptis now handled by my API like in the official API. - Added
Content-Typechecks (like the docs say, meaning it’s required). - While proofreading the docs, I found that
PKCEis written asPCKEin one internal endpoint. (Not fixed yet.) - Small README update (I try to keep it up to date).
Scenario page:
- You can now load a scenario using the GUI.
- Recompiled the Tailwind CSS.
I attached screenshots showing it (you can also see snapshot button but its not implemented YET)
Comments 0
No comments yet. Be the first!
Sign in to join the conversation.