Download the PHP package conedevelopment/blade-filters without Composer

Blade Filters

Use string filters easily in Laravel Blade.

If you have any question how the package works, we suggest to read this post: Laravel Blade Filters.

Getting started

You can install the package with composer, running the composer require conedevelopment/blade-filters command.

Using the filters

You can use the filters in any of your blade templates.

Regular usage:

Chained usage:

Passing non-static values:

Passing variables as filter parameters:

Built-in Laravel functionality:

Limitations

Echos

Laravel supports three types of echos. Raw – {!! !!}, regular – {{ }} and escaped (legacy) – {{{ }}}. Filters can be used only with regular echos. Also, filters cannot be used in blade directives directly.

Why? Raw should be as it is. Forced escaping should be escaped only, without modification.

Bitwise operators

Bitwise operators are allowed, but they must be wrapped in parentheses, since they are using the same "pipe operator".

The Filters

About the filters

Filters are string functions, that are defined in the Pine\BladeFilters\BladeFilters facade. It has several reasons, that are discussed in the Create custom filters section.

The available filters

The package comes with a few built-in filters, also the default Laravel string methods can be used.

Currency

Passing false as the second parameter will align the symbol to the right.

Date

Lcfirst

Unlike PHP's default lcfirst(), this filter works with multi-byte strings as well.

Reverse

Substr

Trim

Ucfirst

Unlike PHP's default ucfirst(), this filter works with multi-byte strings as well.

Supported built-in Str functions

• Str::after()
• Str::before()
• Str::camel()
• Str::finish()
• Str::kebab()
• Str::limit()
• Str::plural()
• Str::singular()
• Str::slug()
• Str::snake()
• Str::start()
• Str::studly()
• Str::title()

Create custom filters

As it was mentioned before, every filter is a method that can be called through the Pine\BladeFilters\BladeFilters facade. It has several reasons why is this approach better, but let's take the most important ones:

• It's easy to define custom filters by extending the facade with the BladeFilters::macro(),
• No extra files, autoloading or class mapping, it's enough to use any service provider to define filters,
• By default Laravel provides a bunch of handy methods that we can use as filters.

Parameter ordering

PHP is not very strict regarding to function's parameter ordering and this way it's easier to coordiante or override them. Also, sometimes it happens with Laravel's string functions. It's important that only those functions can be used, that accept the parameters in the following order:

1. The value to be transformed
2. Any other parameter if needed

For example:

Defining custom filters

Since the filters are only methods that are defined in the Str facade and the BladeFilters class, to create filters, you need to create a macro in a service provider's boot() method.

Contribute

If you found a bug or you have an idea connecting the package, feel free to open an issue.