Re: [I] Unable to access swagger API after enabling prefix routing [superset]

["venkatamandavilli-code (via GitHub)" <gi...@apache.org>]

venkatamandavilli-code commented on issue #33304:
URL: https://github.com/apache/superset/issues/33304#issuecomment-4471374123

   Thanks for reporting this issue and sharing the details clearly.
   
   From the behavior described, it seems like the current implementation may not be fully handling this edge case consistently during the render or refresh flow. Situations like this can become especially noticeable in larger dashboards where multiple components depend on shared state or metadata updates.
   
   It may help to narrow down whether the issue happens only after specific user interactions, refresh events, or configuration changes. Comparing the API response with the final rendered behavior could also help identify where the mismatch is occurring.
   
   A focused regression test around this scenario would probably help prevent similar issues going forward as well.
   
   Thanks again for documenting it clearly.
   


-- 
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: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org