I think this feature is quite useful. Most of our contributors contribute
in their spare time out of interest. So, we can't dictate which features
they should complete. Instead, they choose to prioritize and address the
features they are interested in.

Therefore, if you hope to see this feature implemented soon, you are more
than welcome to submit a pull request. Thank you!

Thanks

*Ovilia*


On Tue, Jun 17, 2025 at 3:22 PM Berfu Taluy <berfu.ta...@navara.nl> wrote:

> Hi Ovilia,
>
> Thank you for your reply. We had already considered this workaround, but
> unfortunately, it's not a straightforward solution on our end.
> We’re working with a large volume of data, and our engineers are uploading
> multiple profiles.
> Applying this fix across time series with 10–15 profile uploads would
> significantly impact the client's experience due to delays.
>
> Could you please let us know if this bug is still being actively looked
> into, or if it's no longer being addressed?
>
> Looking forward to your update.
>
> Best regards,
>
> Berfu
>
> Op di 17 jun 2025 om 05:37 schreef Ovilia <oviliazh...@gmail.com>:
>
>> Hi Berfu,
>>
>> I think a quick fix should be adding the same x value for all the series
>> data.
>> Here is a demo:
>>
>> https://echarts.apache.org/examples/zh/editor.html?code=MYewdgzgLgBAJgQygggjAvDA2gKBtsAUwHcYARJQgCgHIAmABjoFYBaBgRnY5gYC4G_QTQCUAGhh0AzAF0xeAiXKVajFt3ZTeAoQ1ES6AdjkKsRUhSjV6TNp3YAWbYJ37JdGThkBuHKEiwiMgAQhjYpubKVqq2GkzOum4cHvL4ZkqW1mp2XAxauq7iMBzMJmmRmTHq9gyGCYUGDJ4-OH7g0DCEAB5WYHCEcGiYQagAdBAANgCWwNQivgBmIABOMFQThLBTYQzeMNsAPPBICMGjG2AA5lAAFnsA1PdTIjAA3gobsEsArn1hCwgJhBCL58EtVutNjAAFY7Pawo4jFDnQhXW4Pe7Ql7vfD4KYLNZIrDQmRYJqjS6bAAqUwAtnMMOhhidglgpqTyZSoDT6VQRNiFLiYD8_pgoMtviDBbiAEbLQgIADWoNxAF8FOq8QSqABCEVwAVC7q9fqDUYAB2-EBuVCwI1Z7LJcl4MnmGpw6uNqNNyIgKygVCoCAkMpe6AAfDAEE6YKwYDKnW62gFOj1vQNQsyQuNprM-YsVmtPvs4SXESdkRdrncYI9nm8PlD9f9AcCVeCi1DYZhdjCYOXs1X0bXMYbcfjCSziRyZBTqXSGUys6g2TO59yF3yx0Lm2KJVKhfg5QrldLNTBzxPdfrt6mTRmLVabXaK6unRImm78OrPWm-g-_WWAMgxDMNI2jJpY3jRNfBwEBzSgKZwDCHEYCgEAQAmRDzT4BshWtEBiFw8VJVSXFxSmS5KWWXCaAQLopggGgNTIroUAYiBcNQ_AoAAT3NQhaMQ-kaDI_B6MYgAZBAZUICYuOlMEVlpJArBomAaFeABZVUAHpXjgVVmKFc9VTI3j2MYhShT4gTaIAN0BSVjIvMjgWWKZCE48IhW43ERlwr1_0GMTyP4wSNOmIhRMUqN5QQABlPiNi4szYugBBgEVWiEBc79Qr8_AArvdM4GCUKePC2iosIGLDzihUkt4lK3jS-qMqynK8ovBRPFVbwgA
>>
>> Thanks
>>
>> *Ovilia*
>>
>>
>> On Mon, Jun 16, 2025 at 10:59 PM Berfu Taluy
>> <berfu.ta...@navara.nl.invalid> wrote:
>>
>>> Dear E-Charts Team,
>>>
>>> I hope this message finds you well.
>>>
>>> We're currently working with a client who is encountering the issue
>>> described in the following GitHub ticket:
>>> https://github.com/apache/echarts/issues/15742.
>>>
>>> This issue has been open since 2021, and I added a comment on February
>>> 13th, 2025, but we haven't received any response so far. We're reaching
>>> out
>>> in the hope that someone on your team might be able to take a look or
>>> provide guidance on how we can work toward a resolution.
>>>
>>> Any assistance would be greatly appreciated, as this is impacting our
>>> client's project.
>>>
>>> Thank you in advance for your time and support!
>>> --
>>>
>>> Met vriendelijke groet, Kind regards,
>>>
>>> N A V A R A
>>>
>>> Berfu Taluy
>>> Consultant
>>>
>>> M: +31 653 712 472
>>> T: +31 343 445 677
>>> www.navara.nl
>>>
>>
>
> --
>
> Met vriendelijke groet, Kind regards,
>
> N A V A R A
>
> Berfu Taluy
> Consultant
>
> M: +31 653 712 472
> T: +31 343 445 677
> www.navara.nl
>

Reply via email to