Conclusion on User Signup

What have we done so far?

Many new concepts were introduced in this chapter:

1. We implemented a service to create users and log them in, and we tested that service.

2. that service. We then created a feature module, configured its routing, and consumed our service within a component.

3. We also learned how to test this component. We’ll get to E2E testing in the next chapter, once we create the dashboard.

This chapter was dense. As was mentioned, this may be the most difficult section of the entire course. Creating and authorizing users isn’t the most straightforward thing to learn, or explain, but it’s necessary to address upfront. On top of this, we also introduced many strange concepts like fixture, debugElement, and nativeElement within the tests for this feature…

Much of what we learned so far will start to feel more familiar in upcoming chapters, because we’ve already addressed the majority of it here. A bit of repetition with other features should help solidify some of these concepts if they’re still a bit confusing right now.

At this point, we can commit our latest changes and push these changes up to GitHub.

Note: Git may ask you to set your account’s identity before committing changes to the GitHub. For this, use the following commands to set your email address and username.

git config --global user.email "you@example.com"
git config --global user.name "Your Name"

Below are the commands to push changes to the GitHub repository.

git init
git remote add origin https://github.com/your-username-here/lets-get-lunch-fe.git
git add .
git commit -m "Add user signup"
git push origin master

Run the code below and execute the commands in the lets-get-lunch directory.