Book Image

Full Stack Development with Angular and GraphQL

By : Ahmed Bouchefra
Book Image

Full Stack Development with Angular and GraphQL

By: Ahmed Bouchefra

Overview of this book

GraphQL is an alternative to traditional REST technology for querying Web APIs. Together with Angular and TypeScript, it provides a tech stack option for building future-proof web applications that are robust and maintainable at any scale. This book leverages the potential of cutting-edge technologies like GraphQL and Apollo and helps Angular developers add it to their stack. Starting with introducing full-stack development, you will learn to create a monorepo project with Lerna and NPM Workspaces. You will then learn to configure Node.js-based backend using GraphQL, Express, and Apollo Server. The book will demonstrate how to build professional-looking UIs with Angular Material. It will then show you how to create Web APIs for your frontend with GraphQL. All this in a step-by-step manner. The book covers advanced topics such as local state management, reactive variables, and generating TypeScript types using the GraphQL scheme to develop a scalable codebase. By the end of this book, you'll have the skills you need to be able to build your full-stack application.
Table of Contents (16 chapters)
1
Part 1: Setting Up the Development Environment, GraphQL Server, and Database
7
Part 2: Building the Angular Frontend with Realtime Support
13
Part 3: Adding Realtime Support

Persisting the component state with reactive variables

In the previous chapter, we implemented some methods that allow us to like and comment on posts. However, there's one issue with this – after commenting or liking the post, the post element will be initialized and properties such as commentsShown will have an initial value of false, which will hide the comment box (and the comments' feed later) and display the latest comment.

This is not quite the intended behavior since we don't want the component to reset its internal state each time the user comments or likes a post. Instead, the user should be presented with the comment box and the comments' feed (which will be implemented later) until they choose to hide them.

The following screenshot shows a post once it's been liked and commented on:

Figure 11.1 – A post once it's been liked and commented on

This feature's implementation is a good candidate...