natwar585 opened a new issue, #31694:
URL: https://github.com/apache/superset/issues/31694

   ### Bug description
   
   I am currently working on embedding a chart from Apache Superset into an 
Angular application. The chart displays correctly within Superset itself, but 
when I try to display it in my Angular app, it does not render as expected.
   
   Here are some details about the issue:
   
   The chart shows up fine when accessed directly in Superset.  but i try my 
angular app then Some charts and tables load fine, but others fail to render
   
   I have attached images showing the Superset dashboard and the Angular app 
dashboard for reference. The issue is visible in the Angular app, where certain 
elements do not render 
   
   ### Screenshots/recordings
   
   ![Screenshot from 2025-01-03 
14-28-37](https://github.com/user-attachments/assets/aadfeb9d-968f-4d64-8096-242f4ba9aa6e)
   ![Screenshot from 2025-01-03 
12-53-18](https://github.com/user-attachments/assets/b747b4e1-bee4-46fe-8d2e-a0af3dd6cd61)
   
   
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.9
   
   ### Node version
   
   16
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   _No response_
   
   ### Checklist
   
   - [X] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [X] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [X] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


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