Unless some libraries depend on jQuery, don’t introduce jq. If it can be written in ng, don’t use jq...
ng's built-in DOM operation is sufficient. Moreover, ng applications should not manually operate the DOM except for directives. If you want to use jq, it is in the directive.
Angular Js has its own one called jqlite, which is roughly similar to jQuery in usage, but not as complete; If you reference the complete jQuery library in the header, you don’t need to consider jqlite.
Unless some libraries depend on jQuery, don’t introduce jq. If it can be written in ng, don’t use jq...
ng's built-in DOM operation is sufficient. Moreover, ng applications should not manually operate the DOM except for directives. If you want to use jq, it is in the directive.
Angular Js has its own one called jqlite, which is roughly similar to jQuery in usage, but not as complete;
If you reference the complete jQuery library in the header, you don’t need to consider jqlite.