Frontend challenge for CrowdComms

This was my first time using Tailwind with Angular. Made for a good prototyping experience however due to the angular host components, doesn't work quite as well as it does with other libraries eg. React. This limitation means often having to go into the SCSS files and apply specific tailwind rules to the :host.

The API limitations around not having a supported way to fetch a specific user created some interesting challenges. I ended up solving them by:

• Using a set seed for all API requests, resulting in consistent results
• Generating my own 'user id' on the frontend, basically just an incrementing int id (0 being the first user, 1 being the next)
• Fetching a specific user by calculating which page they would have been on, and then fetching that page

• New way of injection: Not sure how I feel about this, keeping all injections in the constructor is predicatable. This new syntax can make them lost among other class fields.
• Control flow: Nice! Much easier to read, no more ng template else silliness. Thought the @empty block was super nice QL
• Signals: Decided not to implement signals in this project due to still in early development / not having experience in them. Can't wait to try them out though!