You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consent is checked on every report publication anyway, so it makes sense for consent.ConsentMechanism functions to take an optional Report argument. This can be used to present users with the contents of the report for approval, so they can see exactly what they are consenting to.
Future flows along these lines: users are presented with a raw report and they can modify it prior to giving consent.
Something to think about, the only change required here would be to change the definition of ConsentMechanism from Callable[[], bool] to Callable[[Optional[Report]], bool].
As it stands now, this would introduce a circular dependency between humbug.consent and humbug.report, so we would have to move Report into another file (e.g. data.py).
The text was updated successfully, but these errors were encountered:
Consent is checked on every report publication anyway, so it makes sense for
consent.ConsentMechanism
functions to take an optionalReport
argument. This can be used to present users with the contents of the report for approval, so they can see exactly what they are consenting to.Future flows along these lines: users are presented with a raw report and they can modify it prior to giving consent.
Something to think about, the only change required here would be to change the definition of
ConsentMechanism
fromCallable[[], bool]
toCallable[[Optional[Report]], bool]
.As it stands now, this would introduce a circular dependency between
humbug.consent
andhumbug.report
, so we would have to moveReport
into another file (e.g.data.py
).The text was updated successfully, but these errors were encountered: