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.

Sign up for GitHub

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

Jump to bottom

Disambiguate whether a revalidator recognized a request when checking for a need to revalidate #87

Merged
merged 2 commits into from
Sep 29, 2020
Merged

Disambiguate whether a revalidator recognized a request when checking for a need to revalidate #87

merged 2 commits into from
Sep 29, 2020

Commits on Sep 29, 2020

  1. feat(revalidator): add handled bool 

    Previously, the revalidators were very ambiguous in identifying if they had actually handled a
request for a revalidation check or not -- a "nil, nil" or "voucher result, nil" was interpreted as
not being handled. This is unfortunate, cause particularly a "voucher result, nil" is an indication
the request is handled by this check, and we should stop processing other revalidators that might
override the value with "nil, nil". We now add a boolean to disambiguate whether the revalidator
"recognized" this request --- if true, processing stops.
    @hannahhoward
    hannahhoward committed Sep 29, 2020
    Configuration menu
    Copy the full SHA
    69f6fdf View commit details
    Browse the repository at this point in the history

  2. style(comments): fix types

    @hannahhoward
    hannahhoward committed Sep 29, 2020
    Configuration menu
    Copy the full SHA
    a400317 View commit details
    Browse the repository at this point in the history