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

   <!-- Answer -->
   There isn't a built-in Superset UI control to prevent legend overlap in 
ECharts when there are many legend entries. However, the ECharts plugin in 
Superset does support advanced legend configuration, including scrolling, via 
the chart options. The relevant code shows that legend properties like 
`legendType`, `legendOrientation`, and `scrollDataIndex` are passed to ECharts, 
and the helper `getLegendProps` manages legend display and scrolling logic. 
This means you can potentially enable legend scrolling (which prevents overlap) 
by setting `legend.type: 'scroll'` in the chart's custom JSON configuration if 
your chart type and Superset deployment expose this option. See the legend 
configuration logic 
[here](https://github.com/apache/superset/blob/98b35125c2a562bb2a61a26e6acd3430339320aa/superset-frontend/plugins/plugin-chart-echarts/src/Timeseries/transformProps.ts).
   
   Recent pull requests have improved legend pagination and usability for long 
legends, but they do not directly solve the overlap when the legend is too 
large for the chart area—scrolling or truncation must be enabled via 
configuration if available in your chart controls [PR 
#33779](https://github.com/apache/superset/pull/33779) [PR 
#33728](https://github.com/apache/superset/pull/33728).
   
   If your chart's control panel does not expose legend scrolling, you may need 
to use the "Customize" or "Advanced" section to inject custom ECharts JSON, or 
request this as a feature for your deployment. There are no existing tickets or 
documentation that directly address this issue.
   
   
   <!-- 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/2f5f7d23-be2e-437d-80af-e99c60204537?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/2f5f7d23-be2e-437d-80af-e99c60204537?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/2f5f7d23-be2e-437d-80af-e99c60204537?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/2f5f7d23-be2e-437d-80af-e99c60204537?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/2f5f7d23-be2e-437d-80af-e99c60204537?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/2f5f7d23-be2e-437d-80af-e99c60204537?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/2f5f7d23-be2e-437d-80af-e99c60204537?feedback_type=other)</sup>&nbsp;&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/33880)


-- 
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