Closed medmouine closed 3 years ago
Also it would be great to have tags or releases to be able to identify which commits to check out for specific versions.
Also the issue comes from the headerDecoder
signature taking Posix -> ServerState -> Json.Decode.Decoder Protocol.RequestContext
instead of the provided Protocol.RequestContext
Actual fix for 3.0.0:
headerDecoder : Posix -> ServerState -> Json.Decode.Decoder Protocol.RequestContext
headerDecoder p serverState =
Json.Decode.oneOf
[ Json.Decode.map Protocol.Cookied (Json.Decode.field "cookie" Json.Decode.string)
, Json.Decode.succeed Protocol.Anonymous
]
Can you clarify why exactly headerDecoder
need a posix argument in 3.0.0 compared to previous versions?
Thanks @medmouine for the prompt. I've written a release note for 3.0.0 https://github.com/choonkeat/elm-webapp/releases/tag/3.0.0 where I linked to freshly written comments wrt type signature changes in the commits.
Hope the notes helps 🙇
Can you clarify why exactly headerDecoder need a posix argument in 3.0.0 compared to previous versions?
The new Time.Posix
argument holds the current time and is useful when you need to verify if the JWT has expired
Hi there are some signature incompatibilities between 2.0.0 and 3.0.0. Could you please provide a change log or something, so it would be easier to see what changed exactly between each version? I would be interested in contributing to the project in the future, but I would need some more clarity in the road map and planned features to set my self up. Thank you!
The signature issue was fixed by downgrading to from 3.0.0 to 2.0.0.
Related trace: