Skip to content

re: Client-side caching with Angular (Part 2) - Versioning VIEW POST


Have you considered this scenario?

  • can use the new field if present
  • purge cache if the field is not present and re-request it
  • remove the handling when the field is not present

This way, you have three separate releases instead of one, but the technique can be applied to many kinds of breaking change.


I'm not sure I'm understanding your approach. When you talk about having a temporal handling do you mean adding a temporal logic in the components to ask if the value is present?

code of conduct - report abuse