NoMongo: Inconsistencies in graphql schema

[Nikhilh26]

Describe the bug
After setting up talawa-admin and talawa-api there alot of inconsistencies in graphql schema in the frontend and the backend schema
To Reproduce
Steps to reproduce the behavior:

1. Start the talawa-admin on develop-postgres branch
2. Start the talawa-api on develop-postgres branch
3. Try to signup as user/admin

Expected behavior
We should be able to signup

Actual behavior
Errors are thrown which depict inconsistency in the schema

Screenshots
If applicable, add screenshots to help explain your problem.

Additional details

Potential internship candidates

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

• Student Internship Programs talawa#359

[github-actions]

Congratulations on making your first Issue! 🎊 If you haven't already, check out our Contributing Guidelines and Issue Reporting Guidelines to ensure that you are following our guidelines for contributing and making issues.

[Nikhilh26]

I have identified the incosistencies. I can start working on it , but i had few doubts.

1. Do we need confirmedPassword in the talawa-api( I skimmed through files and i don;t think we are storing or using the confirmedPassword anywhere) .
2. From talwa-admin we are sending the orgId but in the talawa-api graphql schema we have not defined it . So , do we need that ?

[palisadoes]

1. Check the develop branch to answer some of your queries.
2. Most queries should include the orgID, refer to develop to validate.
3. @xoldd Can you provide context?

[xoldd]

@Nikhilh26 you're meant to fix the graphql schema on the client side to match them with what's implemented on the api side. The inconsistency is on talawa-admin, so fix that.

There is no need for an organization id on a user sign up because the users are a global entity like organizations and don't have to be tied to any organization for them to sign up. Once they've signed up they can choose the organization they want to join.

[palisadoes]

@xoldd Thanks for the reminder. Closing.

[Nikhilh26]

While signing up , users and admins both are asked about the organization should that be removed as well from the UI?

[Nikhilh26]

@xoldd
In api we have marked confirmed password as required here and in develop we were not using it
develop

[xoldd]

@Nikhilh26 Confirmed password is technically a UX only thing. Removed it in this pull request: #2858

[xoldd]

While signing up , users and admins both are asked about the organization should that be removed as well from the UI?

Yes. The organizations a user is an administrator member of is inferred from their identity when they sign in or sign up. If they aren't an administrator member of any organization, they shouldn't see any organizations to manage on talawa admin.

[Nikhilh26]

So we will have to remove it from the api ql right?

[Nikhilh26]

Hey can we maybe connect on slack?