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

Getting and rating the news periodically


Let's say we need to fetch fresh news twice a day. That means we need a service that runs every 12 hours, sends a request to the news agencies, and rates and saves them in the Firebase Realtime database. Later we will notify the user about the stored news.

Tip

You might ask why we need to store them in the database. We can email them as soon as we have filtered the right news. That is true for email notifications. But what if we needed to show them inside the application?

The first part of this scenario sounds familiar and we have already implemented it in the Collector service. However, we cannot use it right away and we need to modify the business logic a little.

The current Collector service saves the SELECTED news only. In other words, a news item will be persisted to the database, only if the user CLICKS on the checkbox for that item. The challenge is if we change this service to satisfy the automated tasks then we will lose the user interactivity...