Document simplified filters context.

[ghost]

Ping @DavidPersson

UnionOfRAD/framework#41 (comment)

[mariuswilms]

Lets keep mentioning static as both approaches work. Something along the lines of "... $this and static/Context::class can be used..."

[ghost]

static does not work out of the box, it isn't automagically bound to the context class, and defaults to lithium\core\Libraries so in 95% of cases it isn't usable: #1272

An exception is the last filter in the chain, which is inside the actual context class, but using static there and Context:class elsewhere can be confusing.

Context::class works consistently and it works everywhere; thoughts?

[mariuswilms]

Yes, static can only be used when the filter was created inside a static method, they cannot later be bound so they can use static:

class Bar {

    protected static $_foo = 'foo';

    public static function giveFilter() {
        return function() {
            var_dump(static::$_foo);
        };
    }
}

$this will only work if the filter was created inside a concrete method OR you later bound the closure to an object.

My point here is that filters should mostly not have the need to interact directly with methods inside the class. They should be self contained. Yes there are some exceptions for these, you're right, let's not recommend �static but Context::class�.

Thanks for bringing this up.

[mariuswilms]

The following code example block will also need a change:

// always use this
Filters::apply('lithium\storage\Session'

[mariuswilms]

Great that you found out about using "::class" this is way shorter and sweeter.

[mariuswilms]

Will merge this, okay?