Download the PHP package quillstack/validator-interface without Composer
On this page you can find all versions of the php package quillstack/validator-interface. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download quillstack/validator-interface
More information about quillstack/validator-interface
Files in quillstack/validator-interface
Package validator-interface
Short Description Common interface for Validator classes.
License MIT
Homepage https://quillstack.org/
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package validator-interface
Validator interface
Common interface for Validator classes. Full documentation: https://quillstack.org/validator-interface
One method, and two exception interfaces. Something which validates says so by implementing this, and something which fails validation says so by implementing the other — so a caller can tell a value it does not like from a mistake in the code.
Why this exists
Validation is the one part of an application that everybody writes differently, and the one part that everything else needs to be able to ask about. A request wants to know whether what arrived is acceptable; it should not need to know how that was decided.
This is that question as an interface, in its own package, so a package can depend on something validating without depending on how.
Requirements
- PHP 8.1 or newer
Installation
Usage
The exception says which kind of thing went wrong:
Catching it is then catching one thing:
Technical documentation
| Interface | What it means |
|---|---|
ValidatorInterface |
validate(): bool — the thing validates something |
ValidatorExceptionInterface |
something went wrong in a validator |
ValidationExceptionInterface |
the value was wrong, which is the usual case; extends the one above |
validate() answers true or throws. It does not answer false: a caller which ignores the
answer would carry on with a value nobody accepted, and a thrown exception cannot be ignored
by accident.
Who implements it
- quillstack/uri — the scheme and the host of a URI
- quillstack/server-request — what
$_SERVERmust hold - quillstack/response — that a status code is one that exists
There is nothing to run here: a package which only names things has no behaviour to test.
Benchmark
There is nothing here to measure.
This package is an interface. It has no behaviour of its own, so there is no operation to time and no library that does the same nothing to compare it with.
What is worth comparing is an implementation, and the honest place for that table is in whichever package implements it rather than here.
Tests
The rest of Quillstack
This is one component of Quillstack, a PHP framework which is as simple to use as it is strict about what it does.
- quillstack/framework — where validation runs before a controller
- quillstack/server-request — where a request class declares its own rules
- quillstack/storage-interface — the same idea, for files
License
MIT. See LICENSE.
