Skip to content
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

Validations based of the latest entry #731

Merged
merged 3 commits into from
Jul 7, 2022

Conversation

arpancodes
Copy link
Contributor

@arpancodes arpancodes commented Apr 26, 2022

Fixes #730

  • Add validation to prevent duplicate consecutive bed entries.
  • Add validation to ensure the new start_date is not past the last start_date.

@arpancodes arpancodes requested a review from a team as a code owner April 26, 2022 21:21
@arpancodes arpancodes self-assigned this Apr 26, 2022
@@ -108,6 +108,14 @@ def validate(self, attrs):
start_date = attrs["start_date"]
end_date = attrs.get("end_date", None)
existing_qs = ConsultationBed.objects.filter(consultation=consultation, bed=bed)
latest_qs = ConsultationBed.objects.filter(consultation=consultation).latest("id")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This logic will crash if there is no latest bed. you need to add a block that only runs if the latest bed exists.

@arpancodes arpancodes requested a review from vigneshhari May 19, 2022 19:35
@gitguardian
Copy link

gitguardian bot commented May 20, 2022

⚠️ 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
- Generic Private Key 613009a config/settings/base.py 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


🦉 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!

Copy link
Member

@vigneshhari vigneshhari left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need more checks, but this is a good start.

@vigneshhari vigneshhari merged commit f4914b8 into ohcnetwork:master Jul 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Validation issues in ConsultationBed
2 participants