Twig Bridge - no functionality to add rule about slugify HOT 6 OPEN

This configuration would also be appreciated on SF bridge.

Something like this or anything that allow us to addRule for simple cases.

cocur_slugify:
    separator: "_"
    rulesets:
        - default
        - [".",""]

from slugify.

@nei This would be the correct approach for solving this.

When we are talking about just the Twig integration because it could be part of the SF bridge, but it could also mean just straight-up Twig.

Alternatively for Twig we could add a slugfiy_add_rule tag to allow editing rules. I would prefer not to change the call for slugify because I think it should match the PHP methods signature.

from slugify.

You should call addRules() on the Slugify object before you inject it to the Cocur\Slugify\Bridge\Twig\SlugifyExtension constructor.

from slugify.

That's correct. but will only work if we know the rule to be added.
instead the scenario i am talking about is when the rule is not known and will be passed from the twig template.

So something like:

{{name | slugify(null, {'&': 'and'}) }}

As, you can see here the php level code doesn't know the rule but will be passed from template

Regards,

from slugify.

@florianeckerstorfer adding a tag would be a better option ...

I was more talking about the scenario where the Frontend guys don't know anything about the backend and have no knowledge about the configurations, in that scenario they can just pass and new rules directly from the twig template and no change in the backend will be required

from slugify.

@harsain Putting this kind of logic inside your template seems like a good idea to get unmanageable code.

from slugify.