Book Image

Hands-On Full Stack Web Development with Angular 6 and Laravel 5

By : Fernando Monteiro
Book Image

Hands-On Full Stack Web Development with Angular 6 and Laravel 5

By: Fernando Monteiro

Overview of this book

Angular, considered as one of the most popular and powerful frontend frameworks, has undergone a major overhaul to embrace emerging web technologies so that developers can build cutting-edge web applications. This book gives you practical knowledge of building modern full-stack web apps from scratch using Angular with a Laravel Restful back end. The book begins with a thorough introduction to Laravel and Angular and its core concepts like custom errors messages, components, routers, and Angular-cli, with each concept being explained first, and then put into practice in the case-study project. With the basics covered, you will learn how sophisticated UI features can be added using NgBootstrao and a component-based architecture. You will learn to extend and customize variables from Bootstrap CSS framework. You will learn how to create secure web application with Angular and Laravel using token based authentication. Finally, you will learn all about progressive web applications and build and deploy a complete fullstack application using Docker and Docker-compose. By the end of this book, you'll gain a solid understanding of Angular 6 and how it interacts with a Laravel 5.x backend
Table of Contents (13 chapters)

Dealing with Laravel resources

In some previous versions of Laravel, it was possible to use a feature called Fractal, to dealing with JSON web API, but with this new version of Laravel we have the Resources feature, a very powerful tool to dealing with JSON web API.

In this section, we'll see how we can use the Resources feature, so that we can get the most out of our API. A Resource class is a way to transform data from one format to another.

When dealing with resources and transforming them into responses for the client, we basically have two types: an item and a collection. An item resource, as you might have guessed, is basically a one-to-one representation of our model, whereas a collection is the representation of many items. Collections may also have metadata and other navigation information, as we will see later in this section.