Contributor
Creative thinking
1x
2 Issues Created
2x
16 Issues Created
3x
128 Issues Created
4x
1024 Issues Created
Problem Solving
1x
2 Pulls Created
2x
16 Pulls Created
3x
128 Pulls Created
4x
1024 Pulls Created
Practical/Professional Skills
Communication Skills
1x
100th Community Interaction
2x
1000th Community Interaction
3x
10000th Community Interaction
Collaboration
1x
2 Pulls Created
2x
16 Pulls Created
3x
128 Pulls Created
4x
1024 Pulls Created
Community Engagement
1x
100 Activity Points
2x
1000 Activity Points
3x
10000 Activity Points
Leadership
1x
Promoted to a team leader
Learn How to Learn
1x
Completed the course work
Skills to apply digital & technology solutions
1x
1 Project Completed Successfully
2x
2 Projects Completed Successfully
3x
3 Projects Completed Successfully
Critical Thinking
Autonomy And Responsibility
1x
2 issues identified and resolved
2x
16 issues identified and resolved
3x
128 issues identified and resolved
4x
1024 issues identified and resolved
Empathy
Value inculcation
Multicultural Competence
Individual Skills
Creative thinking
Problem Solving
Practical/Professional Skills
Team Skills
Communication Skills
Collaboration
Community Engagement
Leadership
Learn How to Learn
Skills to apply digital & technology solutions
Critical Thinking
Advanced Skills
Autonomy And Responsibility
Empathy
Value inculcation
Multicultural Competence
Cultural Skills
Shared a comment on an issue in coronasafe/care_fe on November 21, 2023 at 9:08:08 PM
Is this up for grabs? How should the UI look?
https://github.com/coronasafe/care_fe/issues/6684#issuecomment-1821681798
Shared a comment on an issue in coronasafe/care_fe on November 18, 2023 at 9:54:48 AM
This is a bigger problem at its core with how route protection and login is being handled and just replacing `window.location.href =` with `navigate()` is not going to solve these issues. For ex. when I am logged out and I navigate to `/shifting/board`, instead of being redirected to `/login` I stay on `/shifting/board` and in those cases, after logging in, it does `window.location.href = window.location.pathname.toString()`, using `navigate` here won't do anything because the path does not change, you have to reload the whole page. Same goes for any other url.
https://github.com/coronasafe/care_fe/issues/6665#issuecomment-1817463174
Shared a comment on an issue in coronasafe/care_fe on November 18, 2023 at 9:40:06 AM
Any reason this project is using [raviger](https://github.com/kyeotic/raviger) which barely anyone has ever heard of and has not been updated since 2022 instead of using the industry standard [React Router](https://github.com/remix-run/react-router)?
https://github.com/coronasafe/care_fe/issues/6665#issuecomment-1817458427
Shared a comment on an issue in coronasafe/care_fe on November 17, 2023 at 4:36:46 PM
I can pick this up if still required
https://github.com/coronasafe/care_fe/issues/6503#issuecomment-1816739173
Shared a comment on an issue in coronasafe/care_fe on November 17, 2023 at 4:33:21 PM
@rithviknishad is this under the same category? Only state admin should see this button?
https://github.com/coronasafe/care_fe/issues/6608#issuecomment-1816734216
Shared a comment on an issue in coronasafe/care_fe on November 17, 2023 at 3:49:18 PM
cool, I can take this up. Can you assign it to me? @rithviknishad
https://github.com/coronasafe/care_fe/issues/6660#issuecomment-1816668248
Shared a comment on an issue in coronasafe/care_fe on November 17, 2023 at 3:06:48 PM
This is the function that controls the visibility of the delete button ```typescript const showDelete = (user: any) => { const STATE_ADMIN_LEVEL = USER_TYPES.indexOf("StateAdmin"); const STATE_READ_ONLY_ADMIN_LEVEL = USER_TYPES.indexOf("StateReadOnlyAdmin"); const DISTRICT_ADMIN_LEVEL = USER_TYPES.indexOf("DistrictAdmin"); const level = USER_TYPES.indexOf(user.user_type); const currentUserLevel = USER_TYPES.indexOf(authUser.user_type); if (user.is_superuser) return true; if (currentUserLevel >= STATE_ADMIN_LEVEL) return user.state_object?.id === authUser.state; if ( currentUserLevel < STATE_READ_ONLY_ADMIN_LEVEL && currentUserLevel >= DISTRICT_ADMIN_LEVEL && currentUserLevel > level ) return facilityData?.district_object_id === authUser.district; return false; }; ``` Reproducing the issue, I can see that the delete button is visible because the 3rd `if` condition is evaluating to `true` which because `currentUserLevel > level` which implies that the `authUser` should be able to delete `user` and they also belong to the same `district`. Which makes me think something is wrong on the backend here? Since the logic for showing the button seems to be right. How can I find out why exactly the backend API is failing?
https://github.com/coronasafe/care_fe/issues/6660#issuecomment-1816593105