I did not know about this feature of Phoenix, but the example is mninify-ing the html before sending it. I don’t have enough web background to know, what is a normal response sent as in web frameworks? I never knew you needed to minify the result manually. Is this specific to Phoenix?
In general you rather Munich only stuff that is static, as the minification on the fly may be costly. So instead it often may be better to just pass it as is. However that functionality can be used for other things, for example I have Server-Timing implementation for Plug that uses this feature to record metrics that happened during processing request and send them to the client.
Using this feature to validate that content is valid according to openApi schema on egress (but only in test and dev environments)
I did not know about this feature of Phoenix, but the example is mninify-ing the html before sending it. I don’t have enough web background to know, what is a normal response sent as in web frameworks? I never knew you needed to minify the result manually. Is this specific to Phoenix?
In general you rather Munich only stuff that is static, as the minification on the fly may be costly. So instead it often may be better to just pass it as is. However that functionality can be used for other things, for example I have
Server-Timingimplementation for Plug that uses this feature to record metrics that happened during processing request and send them to the client.Ah, thank you for the reply. That makes sense.