Use Validatable's conformance for UpdateRequest

This allows one to use the simpler Validatable conformance for creating validations instead of the one from UpdateRequest.

You can use this if you don't need the existing model nor the Request and if your validations don't need to be created asynchronously.

3.0.0 RC 5

Compatibility with Vapor 4.22.0 and up.

Version 3.0.0 RC 4

Changed

• UpdateRequest no longer inherits from ValidatableRequest

Version 3.0.0 RC 3

Changed

• use function name updateAuthenticatable for UpdateRequests where Model conforms to Authenticatable to prevent name clashes for other conditional extensions that could make sense in the future.

Version 3.0.0 RC 2

Changed

• Replaced RequestInitializable with RequestMakeable which allows for asynchronous making of the conforming types

Version 3.0.0 RC 1

Changed

• Added support for Vapor 4 🎉
• Redesigned API

Version 2.1.0

Added

• Added getAllErrors(on worker: Worker) to FieldCache: returns the errors for all fields.

Version 2.0.0 RC 8

Added

• OptionRepresentable protocol (and an extension of Sequence of OptionRepresentable) to make it possible to use the #submissions:selecttag

try req.view().render("index", ["roles": roles.allCases.makeOptions()] on: req)

• Documentation for dealing with html forms (including the select tag)

Changed

• The file input tag leaf file now treats the multiple keyword as a boolean parameter

Version 2.0.0 RC 7

Added

• A Leaf tag for the select HTML element. See #46 for an example of how to use it.

Version 2.0.0 RC 6

Changed

• Consistently default to false for isRequired for all Field initializers

Fixed

• Fixed Swift 5 compiler warnings related to redundant access modifiers
• Make sure a Submission made from a Submittable is also used for making the Submittable's additional fields in Submittable.makeFields