Chat
There was an error: ${error.message}
`); } else { document.getElementById('app').innerHTML = loginHTML; } }; // Shows the chat page const showChat = async () => { document.getElementById('app').innerHTML = chatHTML; // Find the latest 25 messages. They will come with the newest first // which is why we have to reverse before adding them const messages = await client.service('messages').find({ query: { $sort: { createdAt: -1 }, $limit: 25 } }); // We want to show the newest message last messages.data.reverse().forEach(addMessage); // Find all users const users = await client.service('users').find(); users.data.forEach(addUser); }; - ``showLogin(error)`` will either show the content of loginHTML or, if the login page is already showing, add an error message. This will happen when you try to log in with invalid credentials or sign up with a user that already exists. - ``showChat()`` does several things. First, we add the static chatHTML to the page. Then we get the latest 25 messages from the messages Feathers service (this is the same as the ``/messages`` endpoint of our chat API) using the Feathers query syntax. Since the list will come back with the newest message first, we need to reverse the data. Then we add each message by calling our ``addMessage`` function so that it looks like a chat app should — with old messages getting older as you scroll up. After that we get a list of all registered users to show them in the sidebar by calling addUser. Login and signup ---------------- Alright. Now we can show the login page (including an error message when something goes wrong) and if we are logged in call the ``showChat`` we defined above. We’ve built out the UI, now we have to add the functionality to actually allow people to sign up, log in and also log out. .. code:: js // Retrieve email/password object from the login/signup page const getCredentials = () => { const user = { email: document.querySelector('[name="email"]').value, password: document.querySelector('[name="password"]').value }; return user; }; // Log in either using the given email/password or the token from storage const login = async credentials => { try { if(!credentials) { // Try to authenticate using the JWT from localStorage await client.authenticate(); } else { // If we get login information, add the strategy we want to use for login const payload = Object.assign({ strategy: 'local' }, credentials); await client.authenticate(payload); } // If successful, show the chat page showChat(); } catch(error) { // If we got an error, show the login page showLogin(error); } }; document.addEventListener('click', async ev => { switch(ev.target.id) { case 'signup': { // For signup, create a new user and then log them in const credentials = getCredentials(); // First create the user await client.service('users').create(credentials); // If successful log them in await login(credentials); break; } case 'login': { const user = getCredentials(); await login(user); break; } case 'logout': { await client.logout(); document.getElementById('app').innerHTML = loginHTML; break; } } }); - ``getCredentials()`` gets us the values of the username (email) and password fields from the login/signup page to be used directly with Feathers authentication. - ``login(credentials)`` will either authenticate the credentials returned by getCredentials against our Feathers API using the local authentication strategy (e.g. username and password) or, if no credentials are given, try and use the JWT stored in localStorage. This will try and get the JWT from localStorage first where it is put automatically once you log in successfully so that we don’t have to log in every time we visit the chat. Only if that doesn’t work it will show the login page. Finally, if the login was successful it will show the chat page. - We also added click event listeners for three buttons. ``#login`` will get the credentials and just log in with those. Clicking ``#signup`` will signup and log in at the same time. It will first create a new user on our API and then log in with that same user information. Finally, ``#logout`` will forget the JWT and then show the login page again. Real-time and sending messages ------------------------------ In the last step we will add functionality to send new message and make the user and message list update in real-time. .. code:: js document.addEventListener('submit', async ev => { if(ev.target.id === 'send-message') { // This is the message text input field const input = document.querySelector('[name="text"]'); ev.preventDefault(); // Create a new message and then clear the input field await client.service('messages').create({ text: input.value }); input.value = ''; } }); // Listen to created events and add the new message in real-time client.service('messages').on('created', addMessage); // We will also see when new users get created in real-time client.service('users').on('created', addUser); login(); - The ``#submit`` button event listener gets the message text from the input field, creates a new message on the messages service and then clears out the field. - Next, we added two ``created`` event listeners. One for ``messages`` which calls the ``addMessage`` function to add the new message to the list and one for ``users`` which adds the user to the list via ``addUser``. This is how Feathers does real-time and everything we need to do in order to get everything to update automatically. - To kick our application off, we call ``login()`` which as mentioned above will either show the chat application right away (if we signed in before and the token isn’t expired) or the login page. What’s next? ------------ That’s it. We now have a plain JavaScript real-time chat frontend with login and signup. This example demonstrates many of the core principles of how you interact with a Feathers API. If you run into an issue, remember you can find a complete working example `here