Open data-blade opened 1 month ago
Hi @data-blade ! Thanks for opening this issue, it indeed looks to me like a bug - it seems that what we're currently checking is whether or not there is more than one exposure depending on the same node, but I'm not sure why that is the check.
It may take us a bit of time to get to so if you're willing to contribute a fix will be happy to point to give pointers on where to look.
Describe the bug given
exposure_a
andexposure_b
,each with just
model_x
in theirdepends_on
,each only specifying
column_name
.running
exposure_schema_validity
will yield this warning for each exposure and columnTo Reproduce create a simple setup with
exposure_a
,exposure_b
andmodel_x
as described aboveExpected behavior no warning, since
model_x
is the only model in thedepends_on
of each exposure, therefore nonode
property should be neededScreenshots n/a
Environment
Additional context the test passes despite the warning
Would you be willing to contribute a fix for this issue? if time allows