Angular’s default template loading will be cached. The caching service used is $tempalteCache, and the service that sends template requests is $templateRequest. You can have two options:
1. After each $http request template is sent, you call $tempalteCache.remove(url) or removeAll to clear all template caches
2. Use $provide.decorator to rewrite the original $templateRequest and disable caching. In the source code of $templateRequest, you can see that it uses $tempalteCache as the cache by default. You can remove it
. . . . . . . If you use Angular and then write the data into the template, what's the difference between using it and not using it?
The data should be written in the resolve of the route and bound in the template.
Angular’s default template loading will be cached. The caching service used is $tempalteCache, and the service that sends template requests is $templateRequest. You can have two options:
1. After each $http request template is sent, you call $tempalteCache.remove(url) or removeAll to clear all template caches
2. Use $provide.decorator to rewrite the original $templateRequest and disable caching. In the source code of $templateRequest, you can see that it uses $tempalteCache as the cache by default. You can remove it
. . . . . . . If you use Angular and then write the data into the template, what's the difference between using it and not using it?
The data should be written in the resolve of the route and bound in the template.
Add a time parameter page after your template page and it will be reloaded every time. I don’t know if that’s what you mean