-
-
Notifications
You must be signed in to change notification settings - Fork 655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[userTypeFix] API: Remove legacy references to userType
#2108
Comments
I'd like to work on this issue! |
userType
userType
Due to sudden academic commitments, I wouldn't be able to fix the issue in time, hence I have unassigned myself. |
Can I work on this issue? |
@palisadoes I think there is some confusion. There are no references to |
Should it be renamed for clarity or do you feel it should remain, and why? |
I don't think there is any need of renaming. |
Thanks. Closing |
I think there is some mis-interpretation. There are some references of |
@palisadoes There are still some files of this userType Reference. I think we have to remove them, they causing block to progress of my PR too. Though I fixed it , Manik will make a PR as he assigned for this issue. We have to reopen this issue |
Sorry for being inactive. @palisadoes, there is a problem. There are some mutations on which a |
Please ask the contributors on the #talawa-projects slack channel. Many of them worked on the |
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. |
@Manik2708 Are you still working on this? |
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. |
Unassigning. Inactivity |
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. |
Is your feature request related to a problem? Please describe.
We recently updated the code base to replace the authorization mechanism for users from being a
userType
field in the database’s User collection to anappUserProfile
field.Describe the solution you'd like
userType
in the code base.The aim is for the
userType
to be removed, while maintaining the expected functionality of the appDescribe alternatives you've considered
Approach to be followed (optional)
Additional context
userType
adjustmentPotential internship candidates
The text was updated successfully, but these errors were encountered: