RxJS Glossary & Semantics - 20 terms you need to understand! (p.2)

Multicast/Unicast:
• Describes whether multiple Consumers share a single Producer (Multicast) or each Consumer has its own Producer (Unicast).

Cold/Hot Observable:
• A Cold Observable creates a new Producer for each Subnoscription, whereas a Hot Observable shares a single Producer among all Subnoscriptions.

Push/Pull System:
• RxJS Observables push values to Consumers, which is the opposite of pull systems where Consumers request values.

Operator & Operator Function:
• Functions that transform or modify Observables or the values they emit.

Operation:
• A specific action or transformation applied to values in an Observable stream, often set up by operators.

Stream:
• A sequence of values or events flowing from a Producer to a Consumer.

Source:
• An Observable that provides values to another Observable.

Observable Inputs:
• Various types that can be easily converted to Observables.

Notifier:
• An Observable used to trigger actions in another Observable, often used for coordination between Observables.

RxJS Glossary & Semantics - 20 terms you need to understand! (p.3 extended ^_^)

Lazy:
- An observable won't push a value until there is a subnoscription. A common mistake is to forget to subscribe and wonder why nothing is happening.

Memory Leak:
- If you forget to finalize, or to unsubscribe, or put subnoscriptions within subnoscriptions---RxJS observables will live forever and may even cause unexpected behavior because they are still alive when you expected them to be gone.

Angular 17 live!! 🔥

🚀 The Ultimate Angular Adapter for TanStack Query | by Netanel Basal | Nov, 2023 | Netanel Basal
https://netbasal.com/the-ultimate-angular-adapter-for-tanstack-query-fac41b244c6f

Angular Official Docs are pretty great! Security in #Angular is important! 🔐

Things you should remember!!! 👇

🔐 Best Practices

➼ Stay updated with Angular library releases.
➼ Avoid altering Angular core
➼ Steer clear of APIs marked "Security Risk".

🔐 XSS Prevention

➼ Block malicious code entry to DOM.
➼ Angular treats all values as untrusted by default.
➼ Sanitizes values inserted into DOM from templates.
➼ Templates are trusted; avoid creating them with user input.

🔐 Sanitization and Security Contexts

➼ Angular sanitizes values for HTML, styles, URLs.
➼ Context-specific: HTML, Style, URL, Resource URL.
➼ Development mode warnings for sanitization changes.

🔐 Direct DOM API Use & Explicit Sanitization

➼ Use Angular templates over direct DOM interaction.
➼ For unavoidable cases, use Angular sanitization functions.

🔐 Trusting Safe Values

➼ Use DomSanitizer for necessary executable code or URLs.
➼ Context-specific methods liek bypassSecurityTrustHtml.

🔐 Content Security Policy (CSP)

➼ Prevents XSS via web server configuration.
➼ Requires unique per-request nonces for Angular to render styles.

🔐 Enforcing Trusted Types

Use HTTP headers with one of the following Angular Policies:
➼ angular
➼ angular#unsafe-bypass
➼ angular#unsafe-jit
➼ angular#bundler

🔐 Server-side XSS Protection

➼ Avoid creating Angular templates on the server side.
➼ Use templating languages that auto-escape values.

🔐 HTTP-level Vulnerabilities

➼ Built-in support for CSRF/XSRF and XSSI.
➼ Cooperate server and client for anti-XSRF technique.

🔐 Auditing Angular Applications

➼ Follow regular web app security principles.
➼ Audit Angular-specific APIs marked as sensitive.

More in depth look can be found in Docs: https://angular.dev/guide/security