1. 06 Sep, 2020 1 commit
  2. 09 Jul, 2020 6 commits
  3. 09 Jun, 2020 3 commits
  4. 25 May, 2020 4 commits
  5. 17 Feb, 2020 6 commits
  6. 25 Nov, 2019 1 commit
    • Stefan Cameron's avatar
      Provide context parameter to validator functions · c073461d
      Stefan Cameron authored
      This enables what I'm calling _Reactive Validations_: See the
      new example in the README.
      When a custom validator function is called, it now receives a fourth parameter,
      `context`, which is a _type validator context_. This context provides additional
      information about the verification, such as the __original value__ being
      verified (which differs from the first parameter, `value`, as that is the value
      currently being verified, closest to the custom validator itself, e.g. the value
      of element in an array, as opposed to the array itself).
  7. 02 Nov, 2019 1 commit
  8. 28 Oct, 2019 4 commits
  9. 27 Oct, 2019 1 commit
  10. 06 Oct, 2019 5 commits
    • Stefan Cameron's avatar
    • Stefan Cameron's avatar
      Version 2.1.0 release · 45308c7c
      Stefan Cameron authored
    • Stefan Cameron's avatar
      Changes for version 2.1.0 · 3b4bbf5a
      Stefan Cameron authored
    • Stefan Cameron's avatar
      Clarify release instructions · 5c60a736
      Stefan Cameron authored
    • Stefan Cameron's avatar
      Usability feedback · 6ccb8410
      Stefan Cameron authored
      - Provides direct access to all types and qualifiers right
        off the `rtv` object, such as `rtv.STRING` or `rtv.OPTIONAL`.
      - Lifts the restriction on typesets to only have a single
        occurrence of a given type. The same type may now appear
        multiple times in the same typeset, which makes typeset
        composition a lot simpler (e.g. you won't have to a
        custom validator if a value could be the string "foo"
        or a string that begins with "bar").
      - Deprecates `rtv.t` in favor of the more self-explanatory
      - Deprecates `rtv.q` in favor of the more self-explanatory
      - Deprecates `rtv.e` in favor of the more self-explanatory
      - `RtvError`: Don't include the typeset in the print output nor the
        serialization since it could be _very_ long and could bloat log
        unnecessarily since the path and cause should be enough to identify
        most issues (and with the path, it's possible to look at the code
        where the full typeset is defined and see what might have gone
        wrong). NOTE: The typeset is still included as a _property_ of
        the error object; this change just affects what's output to the
        console in event an `RtvError` is thrown (and what's output to
        string if you do `error.toString()`).
      - If an exception is thrown in `impl`, it's no longer wrapped
        in an "outer" exception, so you won't get an error message like
        `"Cannot check value: Cannot check value: Cannot check value:
        Invalid typeset..."` because the invalid typeset was nested
        3 levels deep. You'll just get `"Invalid typeset..."` now
        (or whatever the exception was).
      - Added `yup` as an alternative (kind of...) in the README.
      - Fixed a few typos in the docs here and there.
  11. 10 Sep, 2019 3 commits
  12. 20 May, 2019 3 commits
  13. 24 Mar, 2019 2 commits