From 8e7ebd6040bdca27441d645de3417e120421765a Mon Sep 17 00:00:00 2001 From: markostanimirovic Date: Tue, 10 Dec 2024 00:07:41 +0100 Subject: [PATCH] docs(effects): remove redundant standalone flag --- projects/ngrx.io/content/guide/effects/index.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/projects/ngrx.io/content/guide/effects/index.md b/projects/ngrx.io/content/guide/effects/index.md index d8b883c96a..0162cad5d3 100644 --- a/projects/ngrx.io/content/guide/effects/index.md +++ b/projects/ngrx.io/content/guide/effects/index.md @@ -24,7 +24,7 @@ In a service-based application, your components interact with data through many Imagine that your application manages movies. Here is a component that fetches and displays a list of movies. -import { Component, inject } from '@angular/core'; +import { Component, inject, OnInit } from '@angular/core'; import { CommonModule } from '@angular/common'; @Component({ @@ -33,12 +33,11 @@ import { CommonModule } from '@angular/common'; {{ movie.name }} </li> `, - standalone: true, imports: [CommonModule], }) -export class MoviesPageComponent { +export class MoviesPageComponent implements OnInit { private moviesService = inject(MoviesService); - protected movies: Movie[]; + protected movies: Movie[] = []; ngOnInit() { this.movieService.getAll() @@ -77,7 +76,7 @@ The component has multiple responsibilities: Effects handle external data and interactions, allowing your services to be less stateful and only perform tasks related to external interactions. Next, refactor the component to put the shared movie data in the `Store`. Effects handle the fetching of movie data. -import { Component, inject } from '@angular/core'; +import { Component, inject, OnInit } from '@angular/core'; import { CommonModule } from '@angular/common'; @Component({ @@ -86,7 +85,6 @@ import { CommonModule } from '@angular/common'; {{ movie.name }} </div> `, - standalone: true, imports: [CommonModule], }) export class MoviesPageComponent implements OnInit {