Scale filter not found / incorrect filter config documentation

[jazithedev]

http://symfony.com/doc/master/bundles/LiipImagineBundle/filters/sizing.html#scale

parameters:
    images_quality: 80

liip_imagine:
    resolvers:
        default:
            web_path:
                cache_prefix: images/thumb

    filter_sets:
        cache: ~
        news_image:
            quality: '%images_quality%'
            filters:
                scale: { dim: [ 1000, 666 ] }

AAaaaaaaand it's not working. Returning error:

Could not find filter loader for "scale" filter type

Why documentation is writing about something that is not working???

And, when I'm adding - character before scale: { dim: [ 1000, 666 ] } (based on documentation from Symfony.com), error occurs:

The attribute "name" must be set for path "liip_imagine.filter_sets.news_image.filters".

Where is the most updated documentation for this bundle...?

[robfrawley]

@ktrzos The most updated documentation is the website you linked to, hosted on the official Symfony docs, and automatically re-generated from the ReStructured Text files in this repository at Resources/doc on each push.

As for the scale filter, it was added after the last stable release, so you will need to set you composer version constraint to dev-master or similar if you'd like to use it.

And regarding the configuration formatting issue mentioned, I will look into that further, but it looks like the - was a copy-paste error and should be removed from the examples. I'll confirm such and commit and push the changes shortly. Thanks for the heads-up.

[robfrawley]

@ktrzos Documentation changes have been pushed to address the error you pointed out. It should be available in the generated, online docs shortly; the compilation of them are automatic and quick).

If this and my previous answer resolve your issue, please close this.

[robfrawley]

@ktrzos I accidentally closed this; I generally prefer that the person who opened it closes it as a confirmation that the issue is solved. Please re-open if this is not the case. Thanks!

[jazithedev]

Not a problem :). It's all ok now... I think :D. Thanks for help!