Book Image

Angular Services

By : Sohail Salehi
Book Image

Angular Services

By: Sohail Salehi

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 service


Implementing the prevention is not as easy as the cures. In other words, we cannot use a Firebase object and hold everything over there. Instead we have to use a service to keep track of implemented cures - called prevention, because when they are in place, their role is to prevent something bad from happening.

Take the current noted cure, for example: it says we want to see if an article is within an acceptable range. So if we implement that mechanism inside the Evidence service and keep an eye on how that service deals with defects, we accomplish two major goals.

First, we have the chance to weed out the problematic articles. This is not a big deal, in fact we could do that by adding a simple condition check in the evidence service and we wouldn't need to implement another service to do that for us.

Second, we can analyze the URL related to that problematic article and find out why we ended up with extra long or extra short content and THAT is what we can't accomplish...