Fix metabase lib returning the string "null" as the drill through value #44234
+29
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #44232
Description
This PR is reusing the technique that already existed, in which we'd check if the
:value
is a keyword:null
and returnnil
instead. That logic is now encapsulated in a newdrill-value->js
function.So after we fixed the
:null
- > `"null", we're left with one more transformation.In Clojure,
nil
issequable
, so it was hitting this condition. So we ended up converting an empty list()
into an empty array[]
because of this line.Credits and kudos to @piranha for helping me debug this, and for fixing the latter issue.
How to verify
Follow the repro steps from the original issue and confirm that the value is now a proper JS
null
.Checklist