fix(location): duty doctors and staff for each location in a facility

[aeswibon]

Bug Fix

WHAT

🤖 Generated by Copilot at 15b419f

This pull request adds the feature of assigning and updating duty staff for a location in the asset management module. It also adds localization support for the location management components using the react-i18next module. It modifies the type definitions, models, actions, and api modules to support this feature and improves the code quality and organization. It also adds the Location.json file to the src/Locale/en folder for the English translation of the location-related text.

Proposed Changes

• Adds Duty Staff section to location form
• Stores doctors and staff with each location

Associated Issue

• Fixes Duty doctors and Staff for each Location in a Facility #5364

Screenshot

• Normal: Modal for Assigning Duty Staff
  

• Success: Assigning duty staff
  

• Success: Removing duty staff
  

@coronasafe/care-fe-code-reviewers @coronasafe/code-reviewers

Merge Checklist

• Add specs that demonstrate bug/test a new feature.
• Update product documentation
• Ensure that UI text is kept in I18n files
• Prep the screenshot or demo video for the changelog entry, and attach it to issue
• Request for Peer Reviews
• Completion of QA

HOW

🤖 Generated by Copilot at 15b419f

• Add the Location.json file to the src/Locale/en folder with the key-value pairs for the text in the location management components (link)
• Update the index.js file in the src/Locale/en folder to import and export the Location.json file (link, link)
• Use the useTranslation hook and the t function to enable the localization of the text in the LocationManagement and LocationCard components (link, link, link, link, link)
• Add the UserAssignedModel interface to the AssetTypes.tsx module and import it in the models.tsx and AssetTypes.tsx modules (link, link, link)
• Add the duty_staff_objects field to the LocationModel interface in the models.tsx module and pass it as a prop to the LocationCard component (link, link)
• Add the createFacilityAssetLocationDutyStaff function to the actions.tsx module and the createFacilityAssetLocationDutyStaff property to the routes object in the api.tsx module (link, link)
• Update the AddLocationForm component in the AddLocationForm.tsx module to include the state variables, logic, and UI elements for adding and updating the duty staff for a location (link, link, link, link, link, link, link, link)
• Remove the unused imports of the FacilityModel, LocationModel, and WardModel interfaces from the api.tsx module and move them to a more appropriate place (link, link)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
care-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 3, 2024 1:10pm

[netlify]

✅ Deploy Preview for care-egov-staging ready!

Name	Link
🔨 Latest commit	a530c2b
🔍 Latest deploy log	https://app.netlify.com/sites/care-egov-staging/deploys/65955c976063b40007d71a52
😎 Deploy Preview	https://deploy-preview-6512--care-egov-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[nihal467]

@cp-coder the maximum 3 users limitation per location was discussed in EOD, as I am unable to find it mentioned in the issue

[aeswibon]

@cp-coder the maximum 3 users limitation per location was discussed in EOD, as I am unable to find it mentioned in the issue

Actually, Aakash wanted a validation for limiting the number of staffs assigned to any particular location that's why I added a limit of 3 doctors and 3 staffs per location. I had a talk with him in the EOD.

[nihal467]

@cp-coder don't keep the limitation, remove the maximum limitation

[aeswibon]

@nihal467 I have removed the max limit

[github-actions]

👋 Hi, @cp-coder,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.

---

This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

[github-actions]

👋 Hi, @cp-coder,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.

---

This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

[nihal467]

@cp-coder there is a merge conflict and backend require changes

[github-actions]

👋 Hi, @aeswibon,
Conflicts have been detected against the base branch. Please rebase your branch against the base branch.

---

This message is automatically generated by prince-chrismc/label-merge-conflicts-action so don't hesitate to report issues/improvements there.

[rithviknishad]

Marking as hold as the requirements have changed and a more refined feature "User Availability" will be built that adds more depth and it would replace the "Duty Staff for Locations" feature.

Issue: #6968

[github-actions]

Hi, This pr has been automatically marked as stale because it has not had any recent activity. It will be automatically closed if no further activity occurs for 7 more days. Thank you for your contributions.

[nihal467]

@rithviknishad can you clear the merge conflict , as there are bigger file changes

[bodhish]

Closing this PR due to lack of recent progress.