Update Charting Demo

[ksmith94]

This will update the current charting demo to be based around the Encounter resource. Specifically, it will demo how to create encounter notes.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
medplum-provider	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 7, 2024 0:22am

3 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
medplum-app	⬜️ Ignored (Inspect)	Visit Preview		Jun 7, 2024 0:22am
medplum-storybook	⬜️ Ignored (Inspect)	Visit Preview		Jun 7, 2024 0:22am
medplum-www	⬜️ Ignored (Inspect)	Visit Preview		Jun 7, 2024 0:22am

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/chart.js@4.4.2	None	+1	5.01 MB	chartjs-ci
npm/esbuild@0.21.2	environment, filesystem, network, shell	+23	226 MB	evanw

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/esbuild@0.21.2

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[rahul1]

Very close! Just a few more cleanup items

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud