Closed palisadoes closed 7 months ago
@palisadoes, how are we planning to work on this? 1) Spreadsheet like before and a common PR 2) Everyone gets assigned to this issue and works (Every user can make a separate issue themselves, link it to this parent issue and start working on it)
It was recommended in the slack discussion that this could all be handled by a single person because it was mostly removing unused code.
userType
@palisadoes, after checking more files - I found that some of them are actually bugs. Not all of the code is un-used. Some of the code is making changes in features like Delete org and etc doesn't work.
I'll make separate PRs for each of these fixes so that it's easy to review and merge.
@Cioppolo14 / @palisadoes, please assign
src/components/LeftDrawerEvent/LeftDrawerEvent.tsx
src/components/OrgAdminListCard/OrgAdminListCard.tsx
src/components/UserPortal/OrganizationSidebar/OrganizationSidebar.test.tsx
src/components/UserPortal/SecuredRouteForUser/SecuredRouteForUser.test.tsx
src/GraphQl/Mutations/mutations.ts
src/screens/OrganizationPeople/MockDataTypes.ts
src/screens/OrganizationPeople/OrganizationPeople.test.tsx
src/screens/Requests/Requests.tsx
src/screens/UserPortal/Chat/Chat.test.tsx
src/screens/UserPortal/People/People.test.tsx
src/screens/UserPortal/People/People.tsx
src/screens/Users/Users.tsx
@palisadoes, Will be fixed in their respective PRs:
src/components/LeftDrawerEvent/LeftDrawerEvent.tsx
- to be fixed in 1853src/components/OrgAdminListCard/OrgAdminListCard.tsx
- to be fixed in 1852src/GraphQl/Mutations/mutations.ts
- to be fixed in api 2139-- Have an issue with Orgmember connection API, https://github.com/PalisadoesFoundation/talawa-api/issues/2157:
-- Need to first fix eslint issue in functions:
-- To check:
To be fixed in admin/1852:
schema.graphl
src/components/OrgAdminListCard/OrgAdminListCard.tsx
src/GraphQl/Mutations/mutations.ts
Still API issue:
src/screens/UserPortal/People/People.tsx
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