Download the PHP package surgiie/blade without Composer
On this page you can find all versions of the php package surgiie/blade. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download surgiie/blade
More information about surgiie/blade
Files in surgiie/blade
Package blade
Short Description A extended version of the laravel blade engine so it can be used on any textual.
License MIT
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 blade
Blade
Abandoned
This package is no longer maintained consider using laravel-blade-cli for templating needs.
An extended standalone version of the Laravel Blade engine so that it can be used on any textual file on the fly.
Why?
There are several standalone blade packages out there, but there all meant for html template files where spacing is not important. I wanted the ability to use the blade engine for rendering template files such as yaml during my deployment ci pipelines, and wanted it to work basically on any textual file on the fly. The blade engine trims the output and some compiled directives dont preserve nesting of the rendered content, for example, if you have a file like this:
Each line of the contents of the @include should also be indented by the number of spaces left of the @include directive, but it's not and the rendered result will not match the original file structure in terms of nesting/spacing. This is a problematic when rendering files like yaml where spacing and indentation are semantically important.
Installation
Use
Delete Cached Files
You can delete cached files using the deleteCacheDirectory method:
Tip - Do this before calling render method to force render a file.
Custom Directives
You can create a custom blade directive using the directive method:
Using Components
You may also use Blade x-* components in your file:
Anonymous Components
Using dot notation component tag names, you can specify a component file to render:
Where component.yaml resolves to the file components/yaml or component.yaml file that is relative to the file being rendered, this file can then contain any raw content and will be treated as a anonymous component.
Absolute Paths:
If you want to render a component file using absolute path, use a double dash instead of single dash after the x in tag name, i.e x-- instead of x-:
The above component will resolve to /components/foo/yaml, if that doesnt exist, resolves to /components/foo.yaml or errors out if either dont exist.
Class Components
To specify what component class to use for a component name, you can register the component using the components method:
Then you can use the component in your file:
The engine, will then use the class to render the component.
If you are using this package where a class may not be available at runtime or want to require the class on the fly you can use a php file that returns the class constant:
Then if the component name ends with .php, the engine will attempt to require it on the fly:
