New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Profiler dot client #299
Profiler dot client #299
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool, thanks! i think the approach with a twig function is good enough, but we need to avoid name collisions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like a good fix to me.
Update Changelog Rename extension from slugify to httplug_slugify Rename extension from slugify to httplug_slugify Rename extension from slugify to httplug_slugify
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this PR. I like the way you addressed this problem. A TwigExtension do make sense if there are a lot of values to slugify. However, It might be a bit overkill in this scenario.
Why couldn't modify Collector::getClientRootStacks to return ['slug' => $client]
?
Then we could add a new variable here name clientSlug
or something. That would be a 10 line fix, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that is even simpler, i like it!
@Nyholm Thanks for the suggestions. Changes made |
Excellent. Thank you @sowbiba |
What's in this PR?
Slugify client name used as selector to remove non standard characters
https://www.w3.org/TR/CSS21/syndata.html#characters
Why?
#298
Checklist