💡Feature: Creating a new schema for events

[tamalCodes]

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 ✅

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

[github-actions[bot]]

Hello @tamalCodes, thank you for raising the issue.

Currently, the issue is marked as https://github.com/MilanCommunity/Milan-Backend/labels/%F0%9F%91%B7%F0%9F%8F%BB%E2%80%8D%E2%99%82%EF%B8%8F%20status%3A%20awaiting%20triage which means that work for this issue is on hold and we are waiting for the maintainers/owner to review it and provide you with feedback/suggestions to proceed further.

Feel free to reach out to Tamal on Twitter, or drop a mail at tamalcodes@gmail.com if you think that this issue is of critical priority.

Give us a ⭐ to show some support Happy OpenSource 🚀

[tejaskh3]

Hey what's up @tamalCodes, if you allow me to do then I will love to do this task.

[tamalCodes]

Hi @tejaskh3 , you can start working on the issue, assigning it to you 🚀

📑 Checklist in case you missed something

• Local project setup, .env for the backend.
• Contributing guidelines to be followed.

Please maintain structure, use conventional pull request titles, and avoid spam to avoid closure or bans.

[tejaskh3]

Thankyou!!!

[tejaskh3]

Hey @tamalCodes, I have a small doubt, here you mentioned to make schema in router "The file can be made directly in routes > events > EventSchema.js" is it correct or should i make it in schema>events>EventsSchea.js???

[tamalCodes]

Hey @tamalCodes, I have a small doubt, here you mentioned to make schema in router "The file can be made directly in routes > events > EventSchema.js" is it correct or should i make it in schema>events>EventsSchea.js???

It's a typo from my side, it would have been schema>events>EventsSchema.js Sorry for the confusion, I will update the desc of the issue.

[tejaskh3]

No issues i already got you. But don't know why I am not able to commit my changes. getting some error, and not able to resolve them yet.

[tamalCodes]

No issues i already got you. But don't know why I am not able to commit my changes. getting some error, and not able to resolve them yet.

Please post the errors. Those maybe related to EsLint ? Make sure you are not putting some extra gaps, or putting unused vars.

[tejaskh3]

This is what i am getting when trying to commit changes.

[tamalCodes]

Can you try clearing the node_modules and package-lock.json file and running npm install again ?

[tejaskh3]

Tried that too still not working. Also googled a lot.

[tamalCodes]

Maybe this can help ? https://github.com/typicode/husky/issues/1038 Also we love semantic commits so maybe try this too: git commit -m "feat: added event schema"

[tejaskh3]

Tried this as well, but not working, though the error reduced to one line only from 3, will see it after some time, after finishing this assignment. ;)

[tamalCodes]

I see. Please see to it that you can push the code/make a PR in any way. Would be better if done hastily.

[tejaskh3]

Okay!!! doing it.