Description

Currently, we have Status codes and Status messages that are configured for each of those codes that are being used. The goal is to replace any codes we find, with these , like 200 might be replaced with STATUSCODE.OK and then the message for some cases saying "Internal server error" might be replaced with STATUSMESSAGE.INTERNAL_SERVER_ERROR and so on.

Please ensure that this is done for all the codes in the project.

Screenshots

Browser 🥦

Google Chrome

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no).

Code Cleaning

Why do we need to have id here, considering other schema's id's were not assigned implicitly.

And there is a typo for timestamps here.

I would like to fix this.

🥦 Browser

Google Chrome

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no)

What would you like to share?

under the user folder both ReportProblemSchema.js and userSceham.js are written with bad practice no camel casing used as done by other part of repo.

🥦 Browser

Brave

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no)

Description

• In the contributing guidelines for setting up backend repo, instead of writing backend server, frontend server is written.
• This can be both confusing and misleading for contributors while setting up the project locally.

Screenshots

🥦 Browser

Google Chrome

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no)

Description

Currently, we have Status codes and Status messages that are configured for each of those codes that are being used. The goal is to replace any codes we find, with these , like 200 might be replaced with STATUSCODE.OK and then the message for some cases saying "Internal server error" might be replaced with STATUSMESSAGE.INTERNAL_SERVER_ERROR and so on.

Please ensure that this is done for all the codes in the project.

Screenshots

Browser 🥦

Google Chrome

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no).

Description

Setting up backend Documentation need to be updated according to the current requirement, as it doesn't contain information about google auth credentials.

Screenshots

🥦 Browser

Google Chrome

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no)

Description

With the event schema made, a route must be set up that is responsible for getting the events.
Make sure we are able to fetch all the events AND events with the slug property so that we are able to get the details of one single event.

Also add documentation for the same, in Api.yaml file the documentation would be better for folks who are getting started.

Screenshots

No response

🥦 Browser

Google Chrome

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no)

Description

With the event schema made, a route must be set up that is responsible for adding an event. It would take in all the needed details and create an event in the database.

Also add documentation for the same, in Api.yaml file the documentation would be better for folks who are getting started.

Screenshots

No response

🥦 Browser

Brave

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no)

Description

We need a new schema to be made for the events. These events will be shown later on, and one single club can make multiple events. The properties are mentioned below, more can be added when the PR is made (upon discussion). The file can be made directly in routes > events > EventSchema.js

Properties:

• name : String, Required
• about : String, Required
• hostclubslug : String, Required
• hostclubname : String, Required
• bannerimage : String, Not-Required
• thumbnailimage : String, Required
• mode : String, Required
• address : String, Not-Required
• city : String, Not-Required
• state : String, Not-Required
• country : String, Not-Required
• iframe : String, Not-Required
• date : String, Required
• time : String, Required
• tags : Array of Strings, Required
• isApproved : Boolean, Not required, Default: false
• createdAt : Date, Required
• updatedAt : Date, Required

Screenshots

No response

🥦 Browser

Google Chrome

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no)

https://github.com/MilanCommunity/Milan-Backend/blob/811736276d02ab00026a6ffe4305b9ab329d0778/routes/club/Club.js#L16

Name

Siddharth Chandrakar

Checklist ✅

• I have followed the organisation.
• I will abide by all the global rules stated here.
• NOTE: Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see. Do this by finding your name in the GitHub organisation list and change the dropdown to public.

Description

Description:

Issue:

• UserType input not going to the database as custom input by google auth

Expected Behavior:

• User able to set the userType during creation of user account
• Google auth take that userInput and send that to the database

Screenshots

No response

Browser 🥦

Google Chrome

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no).

Description

With reference to #1078 and #1077, we need the schema to be updated properly.

• We would need a website field (not required) and a iframe field (not required) in the schema.
• We need to make sure that whenever the club is signing up, the fields are updated too as per the data that is received.

Screenshots

No response

🥦 Browser

Brave

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no)

Description

We have removed the /user/contact route and we need to remove it from the documentation too. Here's the link to the /user/contact in the documentation which also needs to be removed.

This can be removed from this file.

Screenshots

Browser 🥦

Brave

Checklist ✅

• I checked and didn't find similar issue
• I have read the Contributing Guidelines
• I am willing to work on this issue (blank for no).