UserState in Notic Meet

Over the past month, we have been dedicating some time to getting the Visual Studio project for Notic Meet in a state where we can begin building the front end. It’s making progress, but it’s still being prepared.

Most recently, we collaborated to implement user state on the client side. We added a User property to a component that can be inherited by each page. This approach ensures that once a user successfully logs in, any page inheriting from the NoticComponent will have access to the User object. This User object can then be utilised to retrieve meeting IDs, user names, and other relevant details. The User property is read-only, with a getter but no setter.

Other notable progress includes incorporating created and modified dates into the models and successfully setting up the Discussion Point, Meeting, and User models. These models are now fully functional and can be persisted to the Mongo database, although the logic to add the correct IDs has yet to be added. We have the database designs for that and need to take the time to make sure that the documents reference the correct document(s).

It has been a slow few weeks, as usual, but progress is still being made. The backend is now at a stage where we can introduce new models, controllers, and services and develop the necessary logic. However, a few remaining tasks are required for authentication. The login and registration functionalities are working smoothly, and JSON Web Tokens (JWTs) are being generated upon login. These tokens are also stored in the browser’s local storage. However, at the moment, we need to utilise them for user authentication. To address this, we need to implement some middleware and make a few other adjustments, most of which we currently have a high-level understanding of, but now we need to get deeper into how that part works.

Please don’t hesitate to let me know if you have any more questions or need assistance with any specific aspect of our project. You can also visit Notic.

Leave a comment