# cache_clean() works

    Code
      cache_clean(cache_folder, "apple")
    Message
      v Deleting 1 token obtained with an old tidyverse OAuth client.
      i Expect interactive prompts to re-auth with the new client.
      ! Is this rolling of credentials highly disruptive to your workflow?
        That means you should rely on your own OAuth client (or switch to a service
        account token).
        Learn more these in these articles:
        <https://gargle.r-lib.org/articles/get-api-credentials.html>
        <https://gargle.r-lib.org/articles/non-interactive-auth.html>
    Output
      [1] TRUE

# cache_load() repairs tokens stored with names != their hash

    Code
      writeLines(out)
    Output
      ! Cache contains tokens with names that do not match their hash:
      * "abc123_c@example.org" (name)
      * '{TOKEN_HASH}_a@example.org' (hash)
      * "def456_d@example.org" (name)
      * '{TOKEN_HASH}_b@example.org' (hash)
        Will attempt to repair by renaming

# token_match() finds a match based on domain

    Code
      m <- token_match("abc_*@example.org", one_match_of_two)
    Message
      i The gargle package is using a cached token for 'jane@example.org'.

# token_match() scolds but returns short hash match when non-interactive

    Code
      m <- token_match("abc_", one_existing)
    Message
      ! Using an auto-discovered, cached token.
        To suppress this message, modify your code or options to clearly consent to
        the use of a cached token.
        See gargle's "Non-interactive auth" vignette for more details:
        <https://gargle.r-lib.org/articles/non-interactive-auth.html>
      i The gargle package is using a cached token for 'a@example.com'.

---

    Code
      m <- token_match("abc_*", one_existing)
    Message
      ! Using an auto-discovered, cached token.
        To suppress this message, modify your code or options to clearly consent to
        the use of a cached token.
        See gargle's "Non-interactive auth" vignette for more details:
        <https://gargle.r-lib.org/articles/non-interactive-auth.html>
      i The gargle package is using a cached token for 'a@example.com'.

---

    Code
      m <- token_match("abc_", two_existing)
    Message
      i Suitable tokens found in the cache, associated with these emails:
      * 'a@example.com'
      * 'b@example.com'
        Defaulting to the first email.
      ! Using an auto-discovered, cached token.
        To suppress this message, modify your code or options to clearly consent to
        the use of a cached token.
        See gargle's "Non-interactive auth" vignette for more details:
        <https://gargle.r-lib.org/articles/non-interactive-auth.html>
      i The gargle package is using a cached token for 'a@example.com'.

---

    Code
      m <- token_match("abc_*", two_existing)
    Message
      i Suitable tokens found in the cache, associated with these emails:
      * 'a@example.com'
      * 'b@example.com'
        Defaulting to the first email.
      ! Using an auto-discovered, cached token.
        To suppress this message, modify your code or options to clearly consent to
        the use of a cached token.
        See gargle's "Non-interactive auth" vignette for more details:
        <https://gargle.r-lib.org/articles/non-interactive-auth.html>
      i The gargle package is using a cached token for 'a@example.com'.

# gargle_oauth_sitrep() works with a cache

    Code
      writeLines(out)
    Output
      2 tokens found in this gargle OAuth cache:
      '{path to gargle oauth cache}'
      
      email         app         scopes hash...   
      _____________ ___________ ______ __________
      a@example.org gargle-clio        {hash...}
      b@example.org gargle-clio        {hash...}

# gargle_oauth_sitrep() consults the option for cache location

    Code
      writeLines(out)
    Output
      i Taking cache location from the `"gargle_oauth_cache"` option.
      1 token found in this gargle OAuth cache:
      '{path to gargle oauth cache}'
      
      email         app         scopes hash...   
      _____________ ___________ ______ __________
      a@example.org gargle-clio        {hash...}

