Re: anyone using Node for back end web development?
@13 I agree about flask. next time I would just go with django, although it wasn't me ultimately that made the flask choice.
There might be some misunderstanding by what I meant by encoders/decoders, which I should have maybe qualified more.
essentially on the frontend, I used a library to create a decoder for my typescript types that would verify that the incoming json was of the specified type, so it was basically a schema checker. the reason that was valuable was that whether incoming data is what is expected by the frontend is verified at the boundary of the application and if there is an error then it is handled right then and there. further it is used to make sure that the code is typesafe and there aren't any surprises somewhere deeper in the app logic when the app would try to access a field that isn't there.
This was actually massively valuable in practice and allowed us to catch bugs much faster, since these errors became trivial to diagnose.
since the backend was python, it couldn't be checked at compile time that the json it was sending to the frontend conformed to the typescript type definition. instead that had to be verified through manual testing, by using the app and seeing if there are any decoding errors from the frontend typescript decoders.
I was thinking of setting up some integration tests to do this automatically, but it was a pretty non-trivial task, so we put up with manual testing instead.
if backend was also typescript, it could be verified at compile time that the outbound and inbound data was conformant and would have altogether removed the need for that sort of testing
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
