Download the PHP package firehed/input without Composer
On this page you can find all versions of the php package firehed/input. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download firehed/input
More information about firehed/input
Files in firehed/input
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 input
Input
An input validation framework with a boring name
Changelog
Concept
Input validation is an important task in any web application, but remains an extremely tedious task. This replaces intermingled checks with a proper data structure that clearly defines the required and optional inputs.
The design reolves around the idea of API-driven design, where each API endpoint is its own object, however does not explicitly require this format
- it is capable of validating for any object that defines the input requirements. What it cannot easily handle is the common pattern of large controlelrs that are respnsible for many URLs, since each URL has its own validation requirements. It's certainly possible to structure your code in a way to make this work, but that is liable to become more complicated than the benefit it provides.
Data handling steps
Raw input is transformed into safe data in two primary steps:
- Parsing
- Validation
Parsing is responsible for transforming the raw input string into an associative array. If your application is structured to do so, this step can be skipped entirely.
Validation is the most useful part of the library - taking a defined set of
optional and required parameters and their types, and comparing the input
values to the spec. The implementation prevents invalid data from being
propagated entirely; it is not possible to create a SafeInput object (which
your application will use) from invalid data!
Upon completion of this process, a SafeInput object is returned that contains
data in accordance with the spec defined by the object implementing
ValidationInterface (missing optional values are null).
Because this library exists to provide trustable data, it will actively prevent
you from second-guessing it; for example, using isset or empty on the data
structure will throw an exception. It is the author's experience that acting
unable to trust your validated data is an anti-pattern and a code smell; if you
insist on doing so, this is not the right tool for you. Forcing trust like this
tends to prevent documentation from driting apart from reality.
Example
A basic example follows:
some_controller_file.php
index.php
