-
Notifications
You must be signed in to change notification settings - Fork 164
Default follow-up is enabled for AFP Influenza subtypes like A & B are inactive by default. #13641
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
Closed
KarnaiahPesula
wants to merge
1
commit into
development
from
bugfix-13640-afp-contacts-should-be-enabled-in-default-configuration
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
INFLUENZA tuples likely wrong: case surveillance disabled for INFLUENZA, A/B marked primary while inactive
Per constructor order (lines 106–115), you set:
If the intent is only “INFLUENZA_A and INFLUENZA_B inactive by default” while keeping INFLUENZA as the active, primary disease with case surveillance enabled, adjust as below.
Apply this diff:
Optional maintainability tweak: add inline argument comments to avoid boolean mis-ordering in future, e.g.
INFLUENZA(/*active*/true, /*primary*/true, /*case*/true, /*aggregate*/false, /*followUp*/false, /*days*/0, /*variant*/true, /*ext*/false, /*extMulti*/false).Run this quick grep to see where these flags drive behavior and confirm no invariants are violated:
🏁 Script executed:
Length of output: 44146
🏁 Script executed:
Length of output: 90
🏁 Script executed:
Length of output: 230
🏁 Script executed:
Length of output: 64
🏁 Script executed:
Length of output: 326
🏁 Script executed:
Length of output: 312
🏁 Script executed:
Length of output: 3107
🏁 Script executed:
Length of output: 0
INFLUENZA tuples have inconsistent defaults: A/B inactive but marked primary; INFLUENZA active but case surveillance disabled
Constructor parameter order (lines 106–115) is:
defaultActive, defaultPrimary, defaultCaseSurveillanceEnabled, ...Current state:
INFLUENZA(true, false, false, ...): active, not primary, no case surveillanceINFLUENZA_A(false, true, true, ...): inactive, primary, case surveillance enabledINFLUENZA_B(false, true, true, ...): inactive, primary, case surveillance enabledThis contradicts typical enum semantics. If INFLUENZA_A and INFLUENZA_B are inactive by design, they should not be marked as primary. If INFLUENZA is the active parent disease, it should be both primary and have case surveillance enabled by default.
Apply this fix:
Optional: Add inline comments to prevent future boolean parameter mix-ups: