-
Notifications
You must be signed in to change notification settings - Fork 5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[MLv2] Implement automatic-insights
drill
#36443
Conversation
Automatic insights drills have some unusual conditions. This adds `metabase.lib.metadata/editable?` and checks it before returning any drills. On settings: In the app, `MetabaseSettings` is a global singleton and the settings are sometimes updated in place. In the JS testing environment several mock settings instances can exist at once, and the global singleton does not necessarily have the values we want for any given test. This PR makes `metabase.lib.metadata/setting` check for `describe` and `it` to see if we're in the testing environment, and to trust the metadata's `settings` in that case.
Current dependencies on/for this PR:
This stack of pull requests is managed by Graphite. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving just so we can get this in and keep the train rolling, but your tests look busted, it would be good to actually test automatic insights drills rather than just testing underlying records a second time
This was introduced by #36443.
This was introduced by #36443.
Automatic insights drills have some unusual conditions. This adds `metabase.lib.metadata/editable?` and checks it before returning any drills. On settings: In the app, `MetabaseSettings` is a global singleton and the settings are sometimes updated in place. In the JS testing environment several mock settings instances can exist at once, and the global singleton does not necessarily have the values we want for any given test. This PR makes `metabase.lib.metadata/setting` check for `describe` and `it` to see if we're in the testing environment, and to trust the metadata's `settings` in that case.
This was introduced by #36443.
[MLv2] Implement
automatic-insights
drillAutomatic insights drills have some unusual conditions.
This adds
metabase.lib.metadata/editable?
and checks it beforereturning any drills.
On settings:
In the app,
MetabaseSettings
is a global singleton and the settingsare sometimes updated in place. In the JS testing environment several
mock settings instances can exist at once, and the global singleton does
not necessarily have the values we want for any given test.
This PR makes
metabase.lib.metadata/setting
check fordescribe
andit
globals to see if this is the testing environment, and to trust themetadata's
settings
in that case.Implements the BE side of #33558.