Skip to content

fix: update icon role names to current EUI canonical names#6704

Open
florent-leborgne wants to merge 1 commit into
elastic:mainfrom
florent-leborgne:fix/update-icon-names-to-eui-canonical
Open

fix: update icon role names to current EUI canonical names#6704
florent-leborgne wants to merge 1 commit into
elastic:mainfrom
florent-leborgne:fix/update-icon-names-to-eui-canonical

Conversation

@florent-leborgne
Copy link
Copy Markdown
Member

Summary

Updates all {icon} role usages in docs-content to use current EUI canonical (snake_case) names, following the icon renaming in elastic/eui#9279.

The old camelCase names continue to work as aliases in docs-builder (via EuiSvgIcons.cs), but this cleans them up at the source so the docs stay in sync with EUI naming going forward.

Replacements made across 19 files:

Old name New name
bellSlash bell_slash
checkCircle check_circle
clockCounter clock_counter
errorFilled error_fill
export external
filterInCircle filter_in_circle
minus_in_circle minus_circle
pipeBreaks line_break
playFilled play_filled
plus_in_circle plus_circle
plus_in_square plus_square
timelineWithArrow timeline_with_arrow
transitionLeftIn transition_left_in
transitionLeftOut transition_left_out
transitionTopIn transition_top_in
transitionTopOut transition_top_out

Related: elastic/docs-builder#3378

Made with Cursor

@florent-leborgne florent-leborgne requested review from a team as code owners May 26, 2026 09:18
@github-actions
Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

Replaces deprecated camelCase icon names with their current snake_case
equivalents following the EUI icon rename in elastic/eui#9279.

Old name              → New name
bellSlash             → bell_slash
checkCircle           → check_circle
clockCounter          → clock_counter
errorFilled           → error_fill
export                → external
filterInCircle        → filter_in_circle
minus_in_circle       → minus_circle
pipeBreaks            → line_break
playFilled            → play_filled
plus_in_circle        → plus_circle
plus_in_square        → plus_square
timelineWithArrow     → timeline_with_arrow
transitionLeftIn      → transition_left_in
transitionLeftOut     → transition_left_out
transitionTopIn       → transition_top_in
transitionTopOut      → transition_top_out

Co-authored-by: Cursor <cursoragent@cursor.com>
@florent-leborgne florent-leborgne force-pushed the fix/update-icon-names-to-eui-canonical branch from 32fa019 to b21ff5d Compare May 26, 2026 09:22
@theletterf
Copy link
Copy Markdown
Member

@florent-leborgne Seems like this one is bringing over Hub commits.

@florent-leborgne florent-leborgne force-pushed the fix/update-icon-names-to-eui-canonical branch from b21ff5d to 2dc68c6 Compare May 26, 2026 09:22
@github-actions
Copy link
Copy Markdown
Contributor

Vale Linting Results

Summary: 3 warnings, 2 suggestions found

⚠️ Warnings (3)
File Line Rule Message
explore-analyze/dashboards/create-dashboard-of-panels-with-ecommerce-data.md 74 Elastic.MenuArrows Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
explore-analyze/dashboards/create-dashboard-of-panels-with-ecommerce-data.md 159 Elastic.MenuArrows Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
solutions/security/detect-and-alert/view-detection-alert-details.md 40 Elastic.Latinisms Latin terms and abbreviations are a common source of confusion. Use 'and so on' instead of 'etc'.
💡 Suggestions (2)
File Line Rule Message
explore-analyze/alerting/alerts/view-alerts.md 89 Elastic.WordChoice Consider using 'turn off, silence' instead of 'mute', unless the term is in the UI.
solutions/observability/incident-management/view-alerts.md 117 Elastic.WordChoice Consider using 'turn off, silence' instead of 'mute', unless the term is in the UI.

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

Copy link
Copy Markdown
Member

@leemthompo leemthompo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

spot check on dev docs owned files lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants