{"id":59581,"date":"2018-05-02T15:24:55","date_gmt":"2018-05-02T09:54:55","guid":{"rendered":"https:\/\/www.vskills.in\/certification\/tutorial\/?p=59581"},"modified":"2024-04-12T14:13:20","modified_gmt":"2024-04-12T08:43:20","slug":"angular-services-and-dependency-injection","status":"publish","type":"page","link":"https:\/\/www.vskills.in\/certification\/tutorial\/angular-services-and-dependency-injection\/","title":{"rendered":"Angular Services and Dependency Injection"},"content":{"rendered":"

Angular Services and Dependency Injection<\/h1>\n

For data or logic that is not associated with a specific view, and that you want to share across components, you create a service<\/em> class. A service class definition is immediately preceded by the @Injectable<\/a><\/code> decorator. The decorator provides the metadata that allows your service to be injected<\/em> into client components as a dependency.<\/p>\n

Dependency injection<\/em> (or DI) lets you keep your component classes lean and efficient. They don’t fetch data from the server, validate user input, or log directly to the console; they delegate such tasks to services.<\/p>\n

Service<\/em> is a broad category encompassing any value, function, or feature that an app needs. A service is typically a class with a narrow, well-defined purpose. It should do something specific and do it well.<\/p>\n

Angular distinguishes components from services in order to increase modularity and reusability.<\/p>\n