cos301-se-2023 / xpose Goto Github PK

Routing from sign up to login is still not working

We're not using the same lint on github and a different one for the frontend

The message broker (RabbitMq) sender and receiver not communicating

But I now know what to do. I will implement the idea soon and hopefully it gets sorted out quickly

I'll add swagger to the services, I'm not sure whether or not to do it after or before refactoring

There's a 400 error, I'll try to integrate and hopefully it will fix the issue

Create a Discord server and invite the client to join for easier communication and updates. Channels for:

• Frontend
• Backend
• Cloud
• Firebase
• AI
• Admin
• Add client

The frontend home page relies on the, I've beefed up the API but the frontend hasn't adapted to that as of yet, fixing the frontend to be able to use the new api

SignatureDoesNotMatchAccess denied.The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.GET 16730316000 /xpose-4f48c.appspot.com/something_1689271325623_meme04.png

The request body is empty and thus cannot access the uid, for some reason this is causing problems for specifically for the delete

When a user signs up the UID should be stored in the sql table.

Querying the sql table to insert uid in the createUser API function is being refused
but if I test it outside of the createUser function on its own file it works.
Please note that the sql query functionality is being imported and used int the createUpser API function.

Its still not looking good, and needs to display map of the where the event is occuring and the join button isn't working, its supposed to show whether you've joined an event or not

The image service doesn't work properly, we will refactor later after demo 2, so we'll take it offline and make use a of a firebase storage library to upload photos

Update me when the profile page is complete so that I can plug in the endpoints and further test it

the api was made, time to integrate

The pictures wont preview.

I was using the gateway as normal and this happened for some reason while trying DELETE http://localhost:8000/e/events/79a3aaed-5965-4f7e-b3d4-05af18a302ba, I'll figure it out later

Gateway API server is running on port 8000
[HPM] Error occurred while proxying request localhost:8000/events/79a3aaed-5965-4f7e-b3d4-05af18a302ba to http://localhost:8004/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
[HPM] Error occurred while proxying request localhost:8000/events/79a3aaed-5965-4f7e-b3d4-05af18a302ba to http://localhost:8004/ [ECONNABORTED] (https://nodejs.org/api/errors.html#errors_common_system_errors)

The back button is not working

The purpose of this service is to post images and manage the likes and comments of each post. It owns a firestore collection called Posts, holding documents that have the following information:
The document id is the same as the id of the event they belong to, this makes referencing much simpler

The event page has three tabbed pages within it, sharing data between them is done using a shared service. However, that service is only loaded if the event page is called and thus a person cannot go directly to messaging without first going to the event page.

However, the service does get data a few moments after the page loads, so there's some hope there

There seems to be an issue in the feature-createEvent branch where all the endpoints do a CORS error, I think we should configure the server settings to resolve it

Ensure that our code badges are up, all necessary documents are linked and so are unit tests and whatever else

Setting up a production database is a top priority at this point, the free tier we're currently using is annoyingly slow

• The page is not responsive
• The text input boxes aren't consistent
• Selected image does not get displayed
• Location input box not autocompleting (must be because of styling issue)
• The modal doesn't show up when there's been an error in the backend (must not only print out success, it should also be danger)

The frontend, needs better way of accessing the uid of the currently logged in user

There are error messages for the codebase, please @sovaria10 and @Duzzii fix the issues to work with our code style

The API is new and improved but the create event page doesn't know that and it needs the map and autocomplete

Event Feed Service

The Event Feed Service serves as a simplified layer for providing a customized feed of events. It shares the database with the Events service but only allows read access and prohibits modifications. The service utilizes a Firebase collection called "Events" where each document represents an event and contains location data and event tags.

Functionality

• Endpoint for Retrieving a List of Events
  This endpoint retrieves a list of events based on a user's ID. The returned events are filtered based on the user's location, their friends, and other publicly available events.

Events Service Endpoints

1. /:id/
   This endpoint is used to retrieve information about an event specified by its ID. The request body includes the fields:

   • image: Image associated with the event.
   • uid: User ID.

2. /:id/like
   This endpoint allows a user to like an event specified by its ID. The request body includes the field:

   • uid: User ID.

3. /:id/invite
   This endpoint is used to invite another user to an event specified by its ID. The request body includes the fields:

   • uid: User ID.
   • invitee_id: ID of the user being invited.

4. /:id/remove
   This endpoint removes a user specified by their ID from an event specified by its ID. The request body includes the fields:

   • uid: User ID.
   • removee_id: ID of the user to be removed.

5. /:id
   This endpoint retrieves detailed information about an event specified by its ID. The request body includes the field:

   • uid: User ID.

Please note that these endpoints are part of the Events service and are responsible for various operations related to events, such as liking, inviting users, and retrieving event details.

This is just a demonstration of github issues

• Doesn't display profile picture
• No section for bio
• Email
• username
• Delete account button

The endpoints need to be made! Only one endpoint though, get participants

This would help with full CICD, firebase is a good option we have

Describe the problem or the reason its not done

We only have very little tests, we need more testing. However, the tests we would make depend on how we structure our code