sebastianludwig opened a new pull request, #21579:
URL: https://github.com/apache/echarts/pull/21579

   <!-- Please fill in the following information to help us review your PR more 
efficiently. -->
   
   ## Brief Information
   
   This pull request is in the type of:
   
   - [x] bug fixing
   - [x] new feature
   - [ ] others
   
   ### What does this PR do?
   
   Add the missing implementation of `splitLine.showMinLine`/`.showMaxLine` to 
radius, angle and single axis. Also add support for these properties to 
`axisLine` for polar angle axis.
   
   ## Details
   
   ### Before: What was the problem?
   
   <!-- DESCRIBE THE BUG OR REQUIREMENT HERE. -->
   
   <!-- ADD SCREENSHOT HERE IF APPLICABLE. -->
   
   https://github.com/apache/echarts/pull/20114 added `splitLine.showMinLine` 
and `.showMaxLine` and implemented it for the cartesian axis. The current 
documentation shows the option to be supported for other axis as well:
   
   * https://echarts.apache.org/en/option.html#radiusAxis.splitLine.showMinLine
   * https://echarts.apache.org/en/option.html#singleAxis.splitLine.showMinLine
   * https://echarts.apache.org/en/option.html#angleAxis.splitLine.showMinLine
   
   However there was simply no implementation in place. This PR fixes that.
   
   Also, while on it, I also added support for these properties to `axisLine` 
for polar angle axis.
   
   ### After: How does it behave after the fixing?
   
   #### The split line fix
   <img width="403" height="435" alt="Screenshot 2026-04-14 at 13 18 06" 
src="https://github.com/user-attachments/assets/1242a36c-62f2-40b7-ab88-68c8fe6ba6fa";
 />
   <img width="436" height="438" alt="Screenshot 2026-04-14 at 13 18 29" 
src="https://github.com/user-attachments/assets/b6bbfe4a-7e55-4e3d-9de5-d56241158ad2";
 />
   <img width="1358" height="452" alt="Screenshot 2026-04-14 at 13 18 50" 
src="https://github.com/user-attachments/assets/18d5c360-e498-414f-975e-c56122e712c3";
 />
   
   #### The axis line feature
   
   <img width="416" height="439" alt="Screenshot 2026-04-14 at 13 19 44" 
src="https://github.com/user-attachments/assets/8bceab15-24e4-4a08-bf9d-2d0ec6fac30d";
 />
   <img width="488" height="443" alt="Screenshot 2026-04-14 at 13 19 59" 
src="https://github.com/user-attachments/assets/8f24695f-fb47-4d2b-b55b-a55f5a7a693a";
 />
   <img width="496" height="447" alt="Screenshot 2026-04-14 at 13 20 15" 
src="https://github.com/user-attachments/assets/255c5f69-b027-45b1-b108-4e2e2f96877b";
 />
   <img width="501" height="441" alt="Screenshot 2026-04-14 at 13 20 29" 
src="https://github.com/user-attachments/assets/aa117e29-df32-4818-a0d5-59bab08ca91f";
 />
   <img width="438" height="441" alt="Screenshot 2026-04-14 at 13 20 44" 
src="https://github.com/user-attachments/assets/80b86f4f-5962-4b4f-9fa7-b079cdab35d7";
 />
   
   ## Document Info
   
   One of the following should be checked.
   
   - [ ] This PR doesn't relate to document changes
   - [ ] The document should be updated later
   - [x] The document changes have been made in apache/echarts-doc#xxx
   
   ## Misc
   
   ### Security Checking
   
   - [ ] This PR uses security-sensitive Web APIs.
   
   <!-- PLEASE CHECK IT AGAINST: 
<https://github.com/apache/echarts/wiki/Security-Checklist-for-Code-Contributors>
 -->
   
   ### ZRender Changes
   
   - [ ] This PR depends on ZRender changes (ecomfe/zrender#xxx).
   
   ### Related test cases or examples to use the new APIs
   
   N.A.
   
   ### Merging options
   
   - [ ] Please squash the commits into a single one when merging.
   
   ### Other information
   
   This is my first PR in this repo. Please let me know if I missed some of the 
conventions.


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