Update Registrations with a User Type - Mobile

[palisadoes]

Is your feature request related to a problem? Please describe.

Currently our application assumes that all persons tracked in the database are Talawa users. This may not be the case in practice. Administrators will require the ability to manage people who either cannot access our apps or don't want to.

Describe the solution you'd like

There are requirements dependent upon the repository

API

1. We need to update the User collection to have a User Type field that could have at a minimum these possible values
   1. App User
   2. Non App User
2. This will need to be a mandatory field
3. Mutations for this field will need to be created for the User and related collections

The aim is that this field will be automatically populated during the registration process. Here are some examples:

1. Registrations through the mobile app would automatically be by an App User
2. Registrations through the User Portal web app would automatically be by an App User
3. Admins may want to manually add Users who may be an App User or a Non App User
4. Persons attending events may need to be checked in. If they are new to the organization, then the event organizer may want to add them as a Non App User

Mobile

We require this from you:

1. Registrations through the mobile app must automatically be by an App User and the DB must be updated accordingly

Describe alternatives you've considered

• N/A

Approach to be followed (optional)

• See above

Additional context
Related issues include:

1. Create an User Type Flag Field talawa-api#1552 (Prerequisite)
2. Update Registrations with a User Type - Mobile #2269
3. Update Registrations with a User Type - Admin talawa-admin#1273

Other

• Valid tests for this must be created as part of the resolution of this issue

Potential internship candidates

• Please read this if you are planning to apply for a Palisadoes Foundation internship Student Internship Programs #359

[imshivam-gupta]

@noman2002 @Kevoniat @Cioppolo14 I would like to work upon this issue. Can you please assign this to me?

[AVtheking]

I would like to work on this issue

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

Unassigning due to inactivity

[imshivam-gupta]

@palisadoes Sir Actually the the linked issue was a prerequisite for this issue which was not solved yet that's why I was waiting.

[imshivam-gupta]

Can I work on both issues from api and mobile so that I can solve this issue fast.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

No activity. Unassigning

[AVtheking]

@palisadoes is the issue still valid as the approached for this issue is being changed and implemented in the backend repo?

[Cioppolo14]

@AVtheking You are right, I am going to close this.