Role by CSV file and by manual insertion

[godaralokesh29]

No description provided.

[m-siya]

For addition to UI, post images of before and after in PR

[m-siya]

UI needs to be improved.

Remove the 'Or Upload CSV'. Add a toggle instead to switch between single member creation and multi member by csv upload

[dvishal485]

Add a toggle instead

Refer to new role page in frontend repo for this. Toggles switches are present there, reuse it.

Also please go through the comments and review notes here.
Quoting the comment here as well. (dtutimes/nix-backend-v2#127 (comment))

MainWebsiteRole and the Role in database are two different concepts.

MainWebsiteRole is basically the role visible to the general public on our main website
While Role is an internal thing which may vary dynamically.

This is required as suppose a person with designation (main website role) Developer can have different roles in the society, some may have the role of superuser, while other person may have some other role (say foo).

This helps to create different views, and permission levels according to the structure of society while putting people in the same team group.

---

Another example,

I'm one of the Coordinator of the society (main website role) but I've the role of Superuser, as superuser have the access to all the routes and endpoints required for technical maintenance.
Yet, another person may have the same designation (main website role) of Coordinator, yet have some lower level of permission, and hence a different role with less permission, say the role named Illustrator.

---

What can you do here?

Directly assume the parameter received is ObjectId of required role, and add that user accordingly.

In the frontend, you fetch all the available roles in the "Add User(s)" page, and give option to user in a dropdown menu to select users role.

For multiple users addition (via CSV), you can follow one of two approaches (or can come up with some other of your own as well)

1. Frontend should read CSV and replace role name given with their ObjectId before sending the API request.
2. Allow Backend to accept role with role name (string) and map strings back to role_id (ObjectId).

Preference: Follow the 1st approach, as it can help to detect error in CSV early.

Additional note for frontend part: Make sure user can download a "sample CSV" (with headers and maybe a dummy user entry), so making the CSV file is intuitive.

[godaralokesh29]

ObjectIDs given to Roles
Toggle between Single Member and Multimember
UI imporved

[dvishal485]

The PR looks good, great work :)
Just one minor change is required, since roles can change overtime, make sure not to hardcode them.

[dvishal485]

Please do not hardcode this, our nix portal is very dynamic. a role which exists today may not exists tomorrow. Take reference from here which fetches the available roles.

nix-frontend-v2/src/pages/Roles/AllRoles/index.tsx

Lines 29 to 45 in 1014fce

	const fetchRoles = () => {
	const rolesEndpoint = "/role";
	API.get(rolesEndpoint)
	.then((rolesResponse) => {
	setRolesList(rolesResponse.data.data);
	setLoading(false);
	})
	.catch((error) => {
	setLoading(false);
	setError(error);
	});
	};
	useEffect(() => {
	fetchRoles();
	}, []);

The roles name as well as id can be accessed as with fields role_name and role_id. For instance -

nix-frontend-v2/src/pages/Roles/AllRoles/index.tsx

Lines 61 to 67 in 1014fce

	<div key={role.role_id}>
	<Collapsible
	label={
	role.role_name.charAt(0).toUpperCase() +
	role.role_name.slice(1).toLowerCase()
	}
	>

[dvishal485]

Make sample data have a valid entry for each role fetched earlier. Like -

  const sampleData = ["name", "email", "role"] + (for role in roles) {
    ["john", "john@doe.com", role.role_name]
  }

Ofc this is a pseudo code for explanation.

[godaralokesh29]

Updates

• Role IDs are now dynamically fetched from /role API instead of being hardcoded.
• CSV export now includes sample data for each role.

[godaralokesh29]

All the newly added Routes are working fine and fixed the Toast errors and also prevly there were same sample IDs being generated but now all IDs generated in "sample.csv" are unique ( just for testing purposes this was something necessary)

...