Persist model integration changes for front end (#22933)
* Add can-manage to databases to help front-end * Only return persisted true when the state agrees * Add event for persisted-info to catch new models and turn on peristence when appropriate * Fix bad threading * Add comment about the case being detected to add the persisted-info * Fix pre-existing bug in expand-db-details where a function was used as the condition
Showing
- src/metabase/api/database.clj 6 additions, 3 deletionssrc/metabase/api/database.clj
- src/metabase/events/persisted_info.clj 45 additions, 0 deletionssrc/metabase/events/persisted_info.clj
- src/metabase/models/persisted_info.clj 3 additions, 1 deletionsrc/metabase/models/persisted_info.clj
- test/metabase/api/database_test.clj 1 addition, 1 deletiontest/metabase/api/database_test.clj
- test/metabase/events/persisted_info_test.clj 19 additions, 0 deletionstest/metabase/events/persisted_info_test.clj
src/metabase/events/persisted_info.clj
0 → 100644
test/metabase/events/persisted_info_test.clj
0 → 100644
Please register or sign in to comment