JavaScript files and HTML templates might be cached by browsers

[mauroservienti]

When attempting exercises that touch the front-end portion of the application, currently built using AngularJS, it might happen that HTML templates are cached by browsers making it very difficult to debug what's going on.

We're moving away from Angular, however it’s not an Angular issue per se. Browsers cache JavaScript and HTML templates by default, thus moving away from Angular doesn’t solve the problem if we still want to have a single page application as client.

The easiest workaround, that we should document, is to disable browser cache, this can be easily achieved using browser debugging tools without clearing browser cache in its entirety.

[adamralph]

@mauroservienti we're already closing PRs to the angular components because we're switching to server side. Should we close this for the same reason?

[mauroservienti]

This one not really, it’s not an Angular issue per se. Browsers cache JavaScript and html templates by default, thus moving away from Angular doesn’t solve the problem if we still want to have a single page application as client. And the problem affects only exercise one where attendees need to change the UI

[adamralph]

@mauroservienti 👍 OK. Could you please reword the title and description? Currently it's all about Angular.

[mauroservienti]

done

[adamralph]

@mauroservienti I just remembered that we already have some stuff about this in https://github.com/Particular/Workshop/tree/03abdcd3187c92e1361a90f9dd84fa12fd653acc#note

Is there anything more we need to add?

[mauroservienti]

Probably add something about the fact that browsers cache can also be disabled by using F12 browser tools, and then we should find a way to remove the problem entirely