Added an alert when no CSV file is uploaded in Upload External Results Page.

[patelaryan7751]

Fixes #2678

Bugs

Added an alert when no CSV file is uploaded to Upload External Results Page.

externalupload.mp4

[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:41AM (UTC)

[netlify]

❌ Deploy Preview Failed. CC: @rithviknishad

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

[patelaryan7751]

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

[developedBySJ]

@patelaryan7751 Can you work on UI?
Align the button properly.

[patelaryan7751]

Hey @developedBySJ , I have improved the UI

[nihal467]

test approved

[khavinshankar]

@patelaryan7751 just a suggestion, usually in care we have all of the action buttons to the right especially in forms, so I think it would be better if the button is right aligned instead of the center, 🤔 what do you think?

[patelaryan7751]

@patelaryan7751 just a suggestion, usually in care we have all of the action buttons to the right especially in forms, so I think it would be better if the button is right aligned instead of the center, thinking what do you think?

@khavinshankar I think it would look odd as there is only one input field but if you want I can do 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>