upgraded raviger to v4

[aeswibon]

Updates

• Fixes Update raviger; breaking changes #2379
• Upgraded to raviger v4
• Remove errors that occurred due to upgradation

[nihal467]

@cp-Coder @gigincg can you check the deploy issue

[aeswibon]

@nihal467 This PR is good for testing

[vercel]

@cp-Coder is attempting to deploy a commit to the Coronasafe Team on Vercel.

A member of the Team first needs to authorize it.

[aeswibon]

@nihal467 Any updates on this PR?

[nihal467]

@cp-Coder test failed

• the heading of the consultation page is having misaligned
• the create investigation button is not working

• view/upload patient button is not working, malfunctioning

• save user button after clicking, is staying in the same page

• save button malfunction in the external result

• noticeboard tab is malfunction, it is showing no data

[aeswibon]

Updates

• Heading of the consultation page is misaligned
• Create Investigation button is not working
• View/Upload Patient Files button is not working
• After clicking the Save User button, the site is still showing the same page
• Save button malfunctions in the external result
• Noticeboard tab is malfunctioning

[aeswibon]

@nihal467 there is no problem with save button in the external result.
In the above photo, the save button is disabled because the csv file is incomplete. It doesn't have local_body column.

[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>

[nihal467]

@cp-Coder test failed

• unable to file consultation

[aeswibon]

@nihal467 that is not a problem in my PR. That's the problem in the whole staging server. Yesterday, a wrong PR was merged which caused that error. That PR has been reverted. So it will probably take some time until that feature is up and running

[nihal467]

@cp-Coder can you merge the latest version, i can't file a consultation update

[aeswibon]

@nihal467 Merged the develop branch. This PR is good for testing.

[nihal467]

test approved

[khavinshankar]

Suggested change

	{!showFullPath && crumbs!.length > 2 && (
	{!showFullPath && crumbs?.length > 2 && (

shouldn't it supposed to be ? instead of !

[aeswibon]

@khavinshankar It should be ! not ?. The reason is crumbs can possibly be undefined because in the new version of raviger, usePath() can return null.

[khavinshankar]

@cp-Coder Is it new syntax?,

[khavinshankar]

@cp-Coder can you check it once please

[aeswibon]

@khavinshankar I have made the changes

[aeswibon]

@khavinshankar I have updated the logic