This is part 2 of a multi-part series on setting up user authentication in a MERN-stack application using JSON Web Tokens. If you haven't been following along, please visit the other posts for a full understanding of the current project: 1. Authentication Basics 2. Token Auth with JWTs Part 1
Write a function that takes a string and returns true if that string is a palindrome (the same forward and backward) and false if it is not. isPalindrome("bob"); // true isPalindrome("baz"); // false **Extra credit**: Make it so spaces, capital letters, and punctuation don't stop something from being a palindrome.
Authentication is the process of allowing a user of your application to create an account, sign in, have specific user permissions, get data that only concerns them as a user, etc. Authentication includes a security concern (we don't want people to be able to see or manipulate each other's data)
Understanding Schemas A "Schema" can be a tough thing to understand at first, but in reality it's pretty straightforward. A Schema for a database is akin to a "Class" in Object-Oriented Programming. Where a class is like a blueprint for creating objects in a program, a Schema is a blueprint
We've covered the basics of making queries in the MongoDB Shell, but since we'll mostly be writing our queries in our server's JavaScript code using Mongoose, it makes sense to understand how Mongoose does queries. We'll be covering basic CRUD (Create, Read, Update, Delete) operations. With Mongoose, you can perform