ZhengRui opened a new issue, #17164:
URL: https://github.com/apache/echarts/issues/17164

   ### Version
   
   5.3.2
   
   ### Link to Minimal Reproduction
   
   _No response_
   
   ### Steps to Reproduce
   
   ```typescript
   
   option = {
     tooltip: {},
     xAxis: [{
       type: 'value',
     }],
     yAxis: [{
       type: 'value',
     }],
     visualMap: [{
       min: 0,
       max: 1,
     }],
     series: [
       {
         name: 'Gaussian',
         type: 'heatmap',
         data: Array.from({length: 10}, (_, i)=> Array.from({length: 10}, (_, 
j) => [i+.5, j+.5, (i+j)/20])).flat(),
       }
     ]
   };
   
   ```
   
   ### Current Behavior
   
   In the [heatmap-large 
example](https://echarts.apache.org/examples/zh/editor.html?c=heatmap-large&lang=ts&version=5.3.2)
 , i can change xAxis and yAxis type to be either `category` or `value`, but in 
my typescript App, it gives error (using the same minimum option as above for 
both the example and my app): 
   "Heatmap on cartesian must have two category axes". However, i hope the axis 
to be `value` type so I can set min and max.
   
   
   ### Expected Behavior
   
   Axis type as `value` should also work in my app as in the heatmap-large 
example
   
   ### Environment
   
   ```markdown
   - OS:
   - Browser:
   - Framework:
   ```
   
   
   ### Any additional comments?
   
   I am curious why with same version, same option, it works in the 
Heatmap-large example but not working in my app. I am wondering if it is 
because I am importing echarts library and then use it in my react project, 
while the example page is using compiled minified echarts through <script> tag .


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