Skip to content

feat: Add config option to require an active consent #566

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 17, 2024

Conversation

bruce-glazier
Copy link
Contributor

Changes

  • Add flag to force the app to wait until a new consent is assigned if there are no active consents
  • This is required to handle race conditions between first sign in and auto-patient creation.

@coveralls
Copy link

coveralls commented Jun 17, 2024

Pull Request Test Coverage Report for Build 9554043271

Details

  • 10 of 13 (76.92%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage decreased (-0.1%) to 84.307%

Changes Missing Coverage Covered Lines Changed/Added Lines %
src/hooks/useConsent.ts 10 13 76.92%
Totals Coverage Status
Change from base Build 9407698402: -0.1%
Covered Lines: 3912
Relevant Lines: 4501

💛 - Coveralls

@bruce-glazier bruce-glazier merged commit aaa79ac into master Jun 17, 2024
3 checks passed
@bruce-glazier bruce-glazier deleted the add-require-consent-flag branch June 17, 2024 20:43
Copy link

🎉 This PR is included in version 12.7.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot added the released Has been released to the package repository (NPM, etc) label Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released Has been released to the package repository (NPM, etc)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants