Download the PHP package guym4c/twig-prop-types without Composer
On this page you can find all versions of the php package guym4c/twig-prop-types. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download guym4c/twig-prop-types
More information about guym4c/twig-prop-types
Files in guym4c/twig-prop-types
Package twig-prop-types
Short Description Prop Types for Twig components
License MIT
Homepage https://github.com/guym4c/twig-prop-types
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 twig-prop-types
twig-prop-types
React prop types, ported to Twig.
Installation
With Composer:
Usage
This package makes guym4c/prop-types accessible in Twig. For documentation on how to use the prop types themselves, refer to that package.
Props in the Twig sense refers to the current context. You can use the only keyword in Twig to stop the context scope being inherited.
The extension constructor requires the current Twig environment and a flag to bypass the prop checker. You will probably want to prevent the validator from running in production, to avoid any performance issues. (This will not prevent default prop values being set.)
Validation
To validate your props, put the following at the top of a template file:
Twig-specific differences
When giving a fully-qualified classname when checking for an instance type, you may use dots instead of backslashes to simplify string escaping issues, and the leading backslash or dot is optional.
Advanced
You may pass additional properties to the constructor:
$twigEnv: the current Twig environment$bypass:$typesGlobal(optional): a custom name for thePropTypesglobal$exclude(optional): context variables to exclude from validation. Variables prefixed with an underscore_(and the types global) are automatically excluded$allowExtraProperties(optional): Whether prop validation should fail if unexpected unexcluded extra props are found in the context (false by default)
Default values
If required, you must set default values of required props after the props() call to ensure that required props fail correctly if not provided.
The props() and defaults() calls are separated by the Twig concatenate operator (~) so that they may be called in the same {{ output block }} without throwing an error. Both of these functions never return a value, so it is safe to do so.
