@tmornini has expressed the importance of having E-Tags. I concur. I feel a small piece of Validator middleware is good enough. Although it is confusing of my existing definition of "Validation". but the specs never lie. Wondering if this is something where "Form validation" would go as well. But feels like more "cache validation" related. Which i'd rather have a bonafied Cache object (perhaps with a .validate (data) api. Ok I think I understand "Validator" better in the spec from writing it out. It's the "Valid" in Cache inVALIDation. /cc @brandondees.
@tmornini has expressed the importance of having E-Tags. I concur. I feel a small piece of
Validatormiddleware is good enough. Although it is confusing of my existing definition of "Validation". but the specs never lie. Wondering if this is something where "Form validation" would go as well. But feels like more "cache validation" related. Which i'd rather have a bonafied Cache object (perhaps with a.validate (data)api. Ok I think I understand "Validator" better in the spec from writing it out. It's the "Valid" in Cache inVALIDation. /cc @brandondees.https://tools.ietf.org/html/rfc7231#section-7.2