I have some notebooks that are exceptionally allowed to import anything. But I rather not rewrite all the downstream dependencies_rules. Maybe @curved-television-6568

are the downstream targets using`__dependents_rules__` ? I'm assuming that is the case, as otherwise you can simply add a targeted rule set for the notebook target.

Ah, to answer the original question, as stated, is "no", there is no way to skip checks. the way to treat it is to add rules that allows whatever you need.

the way to treat it is to add rules that allows whatever you need.

Understood that this is ideal, but say that the "notebooks folder" doesn't have control over this thing it imports. But the importing thing has a dependens_rule.

what I've done in the past (for my own projects), is use macros to setup the rules, so I have one place to more easily adapt the rules declarations as new needs come up, as they always do.

in summary, there's no poking holes in existing rules, only adding more rules or tweaking existing ones.

but coming back to this now (after enough time away that I had to read up a bit), I feel more than ever, that the idea that these are low level constructs that would benefit a great deal by a higher level of abstraction, so you can more clearly simply state intentions, which would boil down to these dependency rules sets.