Skip to content
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

fix: populate param-fields for named fields on public dashboards #44440

Merged
merged 10 commits into from
Jun 19, 2024

Conversation

snoe
Copy link
Contributor

@snoe snoe commented Jun 19, 2024

closes #44231

@ranquild ranquild added the backport Automatically create PR on current release branch on merge label Jun 19, 2024
;; for mbql queries.
(lib.util.match/match-one field-clause [:field (id :guard integer?) _] id)
;; Attempt to get the field clause from the model metadata corresponding to the field.
;; This is the common case for native queries in which mappings from original columns
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't allow mapping between parameters and native models now. This is actually needed for mbql models because they have string-based refs and the above condition with integer? doesn't work. Maybe it's worth updating the comment

@snoe snoe marked this pull request as ready for review June 19, 2024 20:50
@snoe snoe requested a review from camsaul as a code owner June 19, 2024 20:50
@snoe snoe requested a review from a team June 19, 2024 20:50
Copy link

replay-io bot commented Jun 19, 2024

Status Complete ↗︎
Commit dad2af7
Results
⚠️ 1 Flaky
2653 Passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Automatically create PR on current release branch on merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Field values remapping with mixed PK and a FK targeting the same PK is broken in public dashboards
3 participants