The Emoji component should have its dedicated documentation #20114
Labels
Emoji
hasPR
A Pull Request has already been submitted for this issue.
help wanted
Issues and PRs which are looking for volunteers to complete them.
Comments
OskarStark
added
the
help wanted
|
When we created the component, I made a PR with such a page (before its content was moved/fusionned in String) Nothing amazing, but It could probably be a good starting point. |
|
Update: found it #19489 |
javiereguiluz
added
the
hasPR
javiereguiluz
added a commit
that referenced
this issue
Sep 19, 2024
…(MrYamous) This PR was squashed before being merged into the 7.1 branch. Discussion ---------- [Emoji][String] Extract Emoji from String documentation Give a try for #20114 I've mainly copy/paste current documentation, with following changes : - change name for internal ref link (remove string part) - remove a versionadded directive for Inverse Emoji Transliteration (Emoji component was added in 7.1, I think it's not necessary to indicate this feature has been add in 7.1 too) - remove Gitlab and Slack example for transliterating services emojis as short code and replace it with a note to mention which services are available - add a sentence about slug emojis as this part stay in String documentation Commits ------- 2e11836 [Emoji][String] Extract Emoji from String documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
currently, the documentation for the Emoji component is a section in the documentation page of the string component: https://symfony.com/doc/current/string.html#working-with-emojis
This is quite confusing given that this component does not rely on
symfony/string(its input is a PHP string) nor has shortcuts insymfony/stringat all (except in the Slugger, but this has a separate dedicated section in the page).This documentation should be moved to a dedicated page (that could then become the documentation link used on https://symfony.com/components/Emoji)
The text was updated successfully, but these errors were encountered: