Notes File and Folder Structure LIFT: Locate code quickly, Identify code at a glance, Flattest structure possible, Try to be DRY organize code into feature areas one item (service/component/directive) per file General Coding Practices Single Responsibility Principle (example: re-factor data access service to separate services for user and catalog) prefer immutability use small functions Angular Module Organization App Module Core Module: shared singleton services, app-level components (e.
cover image from PluralSight I’m learning Angular right now – as a React.js fangirl. Pluralsight offered a free month of learning in April. I’ve taken advantage of it. Here are some notes on the course Angular Component Communication by Deborah Kurata. Angular Component Communication Introduction components need to communicate with each other, with its template, with the router, can use a service as an intermediary check GitHub repository Communication with a Template template binding, e.
I’m learning Angular right now – as a React.js fangirl. Pluralsight offers a free month of learning in April. I’m taking advantage of it. Here are some notes on the course Angular Services by Brice Wilson. Angular Services What and Why? reusable piece of (single) functionality shared across components (is it like a React hook? 🤔) able to be delivered when and where it is needed components should only contain logic for the view, all other logic should be inside services Creating and Using Services service = basically a TypeScript class @Injectable decorator Provider required Example Service: