Book Image

Angular Services

Book Image

Angular Services

Overview of this book

A primary concern with modern day applications is that they need to be dynamic, and for that, data access from the server side, data authentication, and security are very important. Angular leverages its services to create such state-of-the-art dynamic applications. This book will help you create and design customized services, integrate them into your applications, import third-party plugins, and make your apps perform better and faster. This book starts with a basic rundown on how you can create your own Angular development environment compatible with v2 and v4. You will then use Bootstrap and Angular UI components to create pages. You will also understand how to use controllers to collect data and populate them into NG UIs. Later, you will then create a rating service to evaluate entries and assign a score to them. Next, you will create "cron jobs" in NG. We will then create a crawler service to find all relevant resources regarding a selected headline and generate reports on it. Finally, you will create a service to manage accuracy and provide feedback about troubled areas in the app created. This book is up to date for the 2.4 release and is compatible with the 4.0 release as well, and it does not have any code based on the beta or release candidates.
Table of Contents (15 chapters)
Angular Services
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

The accuracy manager component


This component controls a view with two main parts: in the Prevention column we have all statistics regarding the current (active) prevention solution. It will contain a description about the prevention mechanism, where it is placed, and how many times it was hit during the last run.

In the cure column we have the option to add feedback about the incident that happened after application execution. In other words, the main difference between prevention and cure is that prevention is a read-only in-memory object that is created during the application run cycle, while cure is a CRUD-able Firebase object (CRUD: Create, Read, Update, and Delete) that we have full control over how it is going to be managed within the component's view. The following screenshot summarizes the business logic for this component:

Like a real life problem, in our application cure cannot control the prevention, but prevention may have a chance to delete a specific cure if a condition is met...