NoMongo: Postgres Migration Support for Venues in orgDashboard

[gautam-divyanshu]

Is your feature request related to a problem? Please describe.
Update query and mutations according to the recently migrated develop-postgres branch of talawa-api.

Describe the solution you'd like
Make the schema support the changes

Additional context

Expected:

Potential internship candidates

Please read this if you are planning to apply for a Palisadoes Foundation internship

• Student Internship Programs talawa#359

[amaan-aly246]

@gautam-divyanshu @palisadoes Please assign this issue.
Thanks

[palisadoes]

This issue aims to restore functionality to the app after migrating to a PostgreSQL API back end.

1. This is a high priority issue. It's a prerequisite for our GSoC ideas.
2. The develop branches of Talawa Admin and Talawa API work together. Use those branches to determine the expected behavior of the apps.
3. Compare the operation of Talawa Admin and Talawa API running together in the develop-postgres branch.
4. Submit your PR against the develop-postgres branch and attach a video.

[NishantSinghhhhh]

May I work on this issue if no pull request has been submitted in the last two days?

[amaan-aly246]

@NishantSinghhhhh I'm working on this. It's just I was doing some other issue.

[amaan-aly246]

@palisadoes venuesTable does not have column for capacity but in frontend venues capacity is used so should I omit capacity property from the talawa-admin or add capacity column to the venuesTable ?

[palisadoes]

Add capacity to the API

[amaan-aly246]

@palisadoes updateVenue does not take attachments as argument but createVenue does. Is this intentional ? If it is so should I remove the option of adding attachments from the frontend as well when the user is updating the venue ?

[amaan-aly246]

nevermind just checked develop branch of talawa-api , it has upload option. I'll update the backend then.

[amaan-aly246]

@palisadoes Do I have to update the test files of Venue component since Venue component has been updated because of the migration before raising the PR or is it a separate issue ?

[palisadoes]

All in one PR. We have enough to review.

[amaan-aly246]

@palisadoes . I'm able to do rest of the necessary things but when I try to create venues with attachments of type [Upload!] I get an error : "Variable \"$attachments\" got invalid value {} at \"attachments[0]\"; Upload value invalid." . How should I create type Upload in frontend ?

[palisadoes]

Please use your initiative and propose a solution that will stand the test of time. Evaluate why it is better than other commonly used alternatives.

[NishantSinghhhhh]

@palisadoes Sir I am about to complete my current issue (All functionalities have been restored in action Item will be adding tests now ) , so if possible could you assign this issue to me I will be more than happy to work on this one

[mpdesai90]

@NishantSinghhhhh If the issue has already been assigned, please don't ask to be assigned. We want everyone to get a chance.

[NishantSinghhhhh]

@amaan-aly246 are you still working on this issue , if you need any help do let me know , I will be happy to help you

[Cioppolo14]

@amaan-aly246 Please let us know you are still working on this issue.

[amaan-aly246]

@Cioppolo14 I was busy with my exams (I mentioned this in Slack to peter) and will start working on this now. I’ll raise a PR shortly.

[amaan-aly246]

@palisadoes I have created a PR in talawa-api (3352) for the changes I made to address this issue.

[palisadoes]

Unassigning. Inactivity.

[iamanishx]

@palisadoes can i take this as am wrorking related to this ?

[Doraemon012]

@palisadoes I would like to work on this, please assign this to me.

[Bittukr7479]

@palisadoes I want to work on this issue, please assign me.

[Doraemon012]

@palisadoes I apologize for the delay. The work is in progress, I’ll raise the PR soon.

[palisadoes]

Unassigning. Inactivity