araknafobia11/12/2020, 10:28 PM
. In certain level, it makes extraction type safe however it does not guarantee that we won't forget to populate context with data. Isn't there a better approach to handle this situation?
dave11/13/2020, 2:17 PM
araknafobia11/14/2020, 2:18 PM
I suppose the question is what kind of behaviour would you expect that's different from what we have now?I think I would love to have the extracted context to be available in type safe manner and I expect compiler to check whenever I forgot to provide the expected context. For example, if I failed to provide filter that was suppose to put variable to context, compiler wont help me there and it will fail at runtime regardless of the request. (Anyone with decent test coverage would find this before it become bug of course) Anyway, I think I was more interested in why http4k did not chose to go that way. Was it because missing feature in the language or was it because design choose etc. Regardless, I still love the functional approach http4k brings. Thanks for all the effort!
dave11/14/2020, 3:21 PM