EmbeddedChat VS react-oauth

Don’t propose major changes - start small! The issue should be within your reach and you should have a decent plan on how to solve it. For example, my first issue is adding tooltips to the message toolbox - just a small UI enhancement. Once you have taken the first step, you will gradually take on bigger tasks.

Do check out the project, and if you like it you can star ⭐ it too :) https://github.com/RocketChat/EmbeddedChat

RocketChat/EmbeddedChat - NEW: AUTH (google SSO)

This blog marks the start of a series I am going to write, sharing my journey in the Google Summer of Code Program, with some tips, learnings, and some design decisions which we (me and my mentor) took to shape the EmbeddedChat Project.

I wanted to share this way, where you can get started with creating a component library instantly and naturally (without worrying about learning any other technology). For a detailed approach about why I chose some things over the other, I will be writing bi-weekly blogs about my progress in the EmbeddedChat project. But for now, let's create a simple counter component.

It seems to be simple at first, but it took a lot of research. At first I thought there must be a library that I could use, right? The closest I got was a library called -@react-oauth/google but it wasn't compatible with how RocketChat Google OAuth endpoint handled requests. It needed both acessToken and idToken but here on successful login we could get either accessToken or code object. The idToken is the JWT hashed version of code object. You can read more about it here. So after a while of research, I started implementing a custom hook which could handle this with the plain gapi-script from scratch. But, the gapi-script introduced some errors/warnings. So, I went and fixed the code and published my own library around it.