mikebridge opened a new pull request, #44995: URL: https://github.com/apache/superset/pull/44995
### SUMMARY In the Add Semantic View form, a dependent select (for example Schema, which depends on Database) kept showing the previous choices while its options were being refreshed: during the debounce, while loading, and after a failed refresh. With a Snowflake layer, changing the database briefly offered the previous database's schemas. Dependent choices now become unavailable as soon as their source value changes, and stay unavailable until the matching response arrives, including after a failure. When the new options arrive, a selection that is still valid is kept and an invalid one is cleared. The existing guard against out-of-order responses is unchanged. ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF Not captured yet; see the manual steps below. ### TESTING INSTRUCTIONS - `AddSemanticViewModal` and JSON Forms helper test suites: six new tests fail without the change; 49 pass with it. - Manual: add a semantic view on a Snowflake layer, pick a database and open Schema, change the database and immediately open Schema again: no schema from the previous database should be offered, during loading or after an error. ### ADDITIONAL INFORMATION - [ ] Has associated issue: - [ ] Required feature flags: - [ ] Changes UI - [ ] Includes DB Migration (follow approval process in [SIP-59](https://github.com/apache/superset/issues/13351)) - [ ] Introduces new feature or API - [ ] Removes existing feature or API 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
