Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Entertainment web app w/ (Angular + Node + Typescript) 👨‍💻

angular, mongodb, node, typescript, tailwind-css
Adriano•42,870
@AdrianoEscarabote
A solution to the Entertainment web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


👨‍💻 Hello everyone!

This was my second full-stack project, and I'm thrilled with the outcome. Throughout the development process, I learned some new technologies, which was a bit challenging, but I believe I did a good job.

Technologies used:

Front-end:

  • Angular
  • Typescript
  • TailwindCSS
  • Ngrx
  • Jasmine

Back-end:

  • Node
  • Typescript
  • Express
  • MongoDB

Concepts that are shaping backend architecture:

  • SOLID
  • Dependency Injection
  • Repository Pattern

If you have any suggestions for code improvements, please feel free to share!

Thanks! 😊

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Louisan TCHITOULA•170
    @LTOssian
    Posted over 1 year ago

    Incredible work Adriano ! This is a very impressive solution, especially regarding the handmade authentication.

    One observation

    I noticed in your home page that on within your ngFor directive you are not using a trackBy function to allow Angular to track each item. Thus when clicking on the bookmark button, every movie card is reloaded !

    The trackBy function is used to improve performance by tracking which unique item has changed instead of refreshing all of the items from the loop.

    If you have experience with react, it does the same improvement as giving a unique key to a returned JSX from a map().

    How to fix this ?

    Inside item-list.component.html

    Currently you have something like this :

    <li *ngFor="let item of items"> {item.name} </li>

    You can apply the trackBy like so :

    <li *ngFor="let item of items; trackBy: trackByItem">{item.name}</li>

    trackByItem is a method that has to be declared within your component, and takes in the loop index and the item value associated, then returns a unique value. Here is an example :

    Inside item-list.component.ts

    /**
    * returns a unique ID for Angular 
    * to compare accurately what item has changed
    */
    public trackByItem(index: number, item: Item) {
       return item.id
    }
    

    You can implement this for every ngFor that iterates through values that are dynamic and can be changed by some event action (i.e: when showBookmarkedImg change from false to true :) ) and it is a good practice overall. Hope this helps ! Here is the official documentation on this

    Marked as helpful

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub