dosubot[bot] commented on issue #35026:
URL: https://github.com/apache/superset/issues/35026#issuecomment-3257250675

   <!-- Greeting -->
   Hi @saghatelian! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the 
superset team.
   
   <!-- Answer -->
   This is a confirmed regression in Superset 6.0.0: the table chart search box 
is showing the raw localization key `search.num_records` instead of the 
expected row count string. The root cause is a fragile translation 
workflow—plugin translations like `search.num_records` are registered only for 
the active locale at plugin load time, so if the locale changes or the plugin 
loads before the app's language is set, the translation may be missing and the 
key appears in the UI. This was likely made worse by recent refactoring in PR 
[#34799](https://github.com/apache/superset/pull/34799), which changed how the 
table chart's search box and controls are rendered.
   
   For now, there isn't a documented workaround. If you need a temporary fix, 
you could try ensuring your Superset instance is set to the desired locale 
before loading the table chart, but this may not be reliable. The best next 
step is to monitor for updates or fixes related to plugin translation 
registration and locale handling in future releases. If you have custom locale 
settings, double-check that they're applied before the table chart plugin loads.
   
   Relevant code and technical details:
   - Table chart search box uses `tn('search.num_records', count)` for its 
placeholder, expecting a translated string like "706 records" 
[source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/plugins/plugin-chart-table/src/TableChart.tsx).
   - The translation key is defined in the plugin's 
[i18n.ts](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/plugins/plugin-chart-table/src/i18n.ts),
 but may not be registered for all locales at runtime.
   
   Let me know if you need more technical details or want to discuss possible 
workarounds.
   
   
   <!-- Dosu Comment Footer -->
   *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
   
   ---
   <sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/ff607571-dac7-474a-ac02-58b0d3258186?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/ff607571-dac7-474a-ac02-58b0d3258186?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/ff607571-dac7-474a-ac02-58b0d3258186?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/ff607571-dac7-474a-ac02-58b0d3258186?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/ff607571-dac7-474a-ac02-58b0d3258186?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/ff607571-dac7-474a-ac02-58b0d3258186?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/ff607571-dac7-474a-ac02-58b0d3258186?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat
 with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=githu
 b)&nbsp;[![Join 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/35026)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to