Manahil-Afzal commented on PR #131:
URL: https://github.com/apache/echarts-examples/pull/131#issuecomment-3760869586

   ***@***.****  Thanks for review
    1) Where should I submit ngx-echarts examples?
     2)  Are there any coding standards or demo requirements I should follow
   for ngx-echarts examples?
     3)  Would a live-update chart demo (like updating bars every 2 seconds)
   be acceptable for ngx-echarts examples?
     4) Are there any restrictions or limitations when using ngx-echarts
   features in examples?”
   am still confused on your comment can u clarify more if u don't mind?
   
   On Fri, Jan 16, 2026 at 12:15 AM zangzimi ***@***.***> wrote:
   
   > ***@***.**** commented on this pull request.
   >
   > Thank you for your contribution. This project only includes examples of
   > ECharts itself and should not contain examples under third - party
   > frameworks. In particular, ngx - echarts is not an official ECharts
   > project. Therefore, if you have such a need, you can submit a pull request
   > for usage examples to ngx - echarts. I will close this pull request.
   > Nevertheless, your contribution is highly appreciated.
   >
   > —
   > Reply to this email directly, view it on GitHub
   > 
<https://github.com/apache/echarts-examples/pull/131#pullrequestreview-3669477910>,
   > or unsubscribe
   > 
<https://github.com/notifications/unsubscribe-auth/BRR7QWHETY5VDH5GTBCXLXT4HCM2DAVCNFSM6AAAAACRWQOU5SVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTMNRZGQ3TOOJRGA>
   > .
   > You are receiving this because you authored the thread.Message ID:
   > ***@***.***>
   >
   


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