-
-
Notifications
You must be signed in to change notification settings - Fork 6k
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
Make legendRenderer property public in order to be externally customizable #3445
Conversation
Codecov Report
@@ Coverage Diff @@
## 4.0.0 #3445 +/- ##
=========================================
- Coverage 29.42% 29.2% -0.23%
=========================================
Files 114 117 +3
Lines 12605 13301 +696
=========================================
+ Hits 3709 3884 +175
- Misses 8896 9417 +521
Continue to review full report at Codecov.
|
@nagykatalin I'm okay with this, however please target |
0b26147
to
4d2e335
Compare
I'm ok too, giving the fact other major renderers are already public.
Oh I just saw 4.0 has made viewPortHandler readable, should be fine. The remaining question is shall we change /// The legend object containing all data associated with the legend
@objc open internal(set) lazy var legend = Legend() to full open access for legend object? @jjatie |
I think legend still being readonly is fine. |
Thanks 👍 |
good to have you back:) |
Goals ⚽
The main idea behind this pull request is to make the legend renderer externally customizable and overridable.
Our customer's request was to detect when the user's clicks on a legend and to highlight corresponding line on the chart.
Implementation Details 🚧
By making public the legendRenderer property (similarly to the renderer property) we would like to use our own legend renderer class which stores the exact location of the labels and in this way we can detect if the user clicked on a label or not.