audits: add I_M_ContactEmailButWouldLikeToParticipateInOtherSurveys check - #1723
Conversation
|
Warning Review limit reached
Next review available in: 1 minute Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (5)
WalkthroughAdds an interview audit check that reports an error when a respondent wants to participate in other surveys without providing a contact email. English and French translations, parameterized tests for valid and invalid cases, and audit-check authoring guidance are also updated. Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
222b72d to
23c0738
Compare
|
@kaligrafy , peux-tu sortir les 2 derniers commits dans leur propre PR ? Ca comme pas rapport ici. |
|
Je suis aussi curieux, ceci ne devrait pas être bloqué au niveau du questionnaire ? Genre tu me peux pas répondre que tu veux faire d'autres enquetes sans mettre ton courriel? |
C'est effectivement vérifié dans le questionnaire, mais si le répondant revient à la seciton plus tard, efface son courriel, et qu'il part, on aura perdu l'info et l'audit le détectera automatiquement. |
23c0738 to
25dfce2
Compare
Fait |
Addresses greenscientist's review comment on chairemobilite#1723: adds the missing case where contactEmail is present but wouldLikeToParticipateInOtherSurveys is false, to keep the parametric test table complete.
Addresses greenscientist's review comment on chairemobilite#1723: adds the missing case where contactEmail is present but wouldLikeToParticipateInOtherSurveys is false, to keep the parametric test table complete.
fb1151a to
96d0850
Compare
greenscientist
left a comment
There was a problem hiding this comment.
Tu as encore mis la correction de la PR dans un commit à part... This need to be squashed...
96d0850 to
add8b8b
Compare
C'est corrigé |
| - Segment section configuration accepts additional widget names as an array of strings in the `additionalSegmentWidgetNames` property. The widgets need to be defined in the survey and will be added after the mode questions (#1345). It also includes the option to ask who was driving a vehicle, with the `askSegmentDriver` boolean option (fixes [#1434](https://github.com/chairemobilite/evolution/issues/1434)). | ||
| - Segment section configuration can set an array of fields representing geolocalization by setting the `fieldsWithGeojsonPoint` property. (fixes [#1603](https://github.com/chairemobilite/evolution/issues/1603)). | ||
| - Added various builtin audit checks: home in survey area, survey contactEmail and helpContactEmail validation, missing home, mismatched household members and declared count, missing or invalid vehicle count | ||
| - Audit check `I_M_ContactEmailButWouldLikeToParticipateInOtherSurveys`: flags interviews where the respondent would like to participate in other surveys but did not provide a contact email (ported from od_mtl_2023's v1 `I_M_ContactEmailButAcceptedToBeContacted`). |
There was a problem hiding this comment.
You should regroup all Audit check addition in the same changelog entry.
There was a problem hiding this comment.
The audit checks will be removed from the changelog, as explained in #1727
Should I just remove it from this PR too?
There was a problem hiding this comment.
I removed the changelog, would have been removed anyway in #1727
There was a problem hiding this comment.
@tahini asked me to not put the audit checks in changelogs anyway
…heck Flags interviews where the respondent would like to participate in other surveys (wouldLikeToParticipateInOtherSurveys) but did not provide a contact email. Ports od_mtl_2023's v1 check I_M_ContactEmailButAcceptedToBeContacted, which was dropped in v2 with no replacement. Test coverage includes the case where a contact email is present but the respondent opted out of participating in other surveys.
add8b8b to
c3a7633
Compare
Summary
I_M_ContactEmailButWouldLikeToParticipateInOtherSurveys, which flags an interview when the respondent would like to participate in other surveys (wouldLikeToParticipateInOtherSurveys) but did not provide acontactEmail.I_M_ContactEmailButAcceptedToBeContacted(dropped in v2 with no replacement) using coreInterviewattributes that already exist (wouldLikeToParticipateInOtherSurveys,contactEmail), so no new attribute or config is needed.I_I_ContactEmailcheck.Test plan
I_M_ContactEmailButWouldLikeToParticipateInOtherSurveys.test.ts(parametricit.each), covering: opted-in + email present (pass), not opted-in + missing email (pass), opted-in + empty string email (fail), opted-in + undefined email (fail).yarn workspace evolution-backend test -- auditChecks/checks/__tests__/interview— all 105 tests pass.yarn lint— no new errors/warnings introduced.yarn format— applied.en/frtranslations inlocales/*/audits.json.CHANGELOG.mdentry (individual audit checks aren't tracked there).Summary by CodeRabbit
New Features
Documentation
Tests