[GitHub] [echarts] plainheart opened a new pull request #16764: fix(radar): fix regression bug brought by branch merging.

Mon, 28 Mar 2022 19:48:13 -0700 


plainheart opened a new pull request #16764:
URL: https://github.com/apache/echarts/pull/16764


   ## Brief Information
   
   This pull request is in the type of:
   
   - [x] bug fixing
   - [ ] new feature
   - [ ] others
   
   
   
   ### What does this PR do?
   
   Fix the regression bug fixed in #15985. It seems this was unexpectedly 
brought by the branch merging, related commits might be 
53babd2b4c83e875f8df6c370b356d6b44c1919c, 
841b572ceb37593ec1d9680d0b4ee19e7b138ca1.
   
   ### Fixed issues
   
   - #16762
   
   ## Details
   
   ### Before: What was the problem?
   
   Some parts of the #15985 were missing after merging.
   
   <img 
src="https://user-images.githubusercontent.com/26999792/160522133-257d6961-f600-4ad1-8d87-c1f743f322ef.png";
 width="400">
   
   ### After: How is it fixed in this PR?
   
   Apply back the fix in #15985.
   
   <img 
src="https://user-images.githubusercontent.com/26999792/160522062-24ce97c6-1e3d-4476-ae0b-40edfed710df.png";
 width="400">
   
   ## Misc
   
   <!-- ADD RELATED ISSUE ID WHEN APPLICABLE -->
   
   - [ ] The API has been changed (apache/echarts-doc#xxx).
   - [ ] This PR depends on ZRender changes (ecomfe/zrender#xxx).
   
   ### Related test cases or examples to use the new APIs
   
   Please refer to `test/radar3.html`.
   
   ## Others
   
   ### Merging options
   
   - [ ] Please squash the commits into a single one when merging.
   
   ### Other information
   


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