Assign Bed or Switch Bed button is visible only for Live Patients

[patelaryan7751]

Fixes #2673

Bugs Fixed

Assign Bed or Switch Bed button is visible only for Live Patients

[vercel]

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

Name	Status	Preview	Updated
care-fe	✅ Ready (Inspect)	Visit Preview	Jun 20, 2022 at 2:08AM (UTC)

[netlify]

❌ Deploy Preview Failed. CC: @rithviknishad

Name	Link
🔨 Latest commit	03704b3
🔍 Latest deploy log	https://app.netlify.com/sites/care-net/deploys/62a443b0e351060009d5c93a

[patelaryan7751]

Deploy Preview Ready https://deploy-preview-2675--care-net.netlify.app/

[shivankacker]

Hey @patelaryan7751 can you add this as a commit to #2563 and close this pr ?
Because the UI will be completely changing with that PR so...

[nihal467]

test approved

[patelaryan7751]

Done Changes as per new UI #2563

[patelaryan7751]

Deploy Preview Ready https://deploy-preview-2675--care-net.netlify.app/

[shivankacker]

Rather than removing the button alltogether, can you change it to "Bed History" and make the modal only show the assigned beds table and not let them add any?

[patelaryan7751]

@skks1212 yeah right. Nice idea i am working on it.

[nihal467]

@patelaryan7751 is it good for testing, saw a comment mentioning you are working

[patelaryan7751]

@nihal467 i am working on it

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	Secret	Commit	Filename
757392	Google API Key	2cec8ae	src/Common/env.tsx	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>