• A high-level plugin API for customizing dep inference • A Django plugin that uses the above • A high-level plugin API for “allowed deps” aka “visibility”

@curved-television-6568 has already done a lot of work on visibility -- coordinating with him on reviving that effort would be great. I think we all dropped the ball on reviewing because we were afraid of committing to a particular design

I think pairing/having more eyes on that design is required, yes. I did quite a bit of work, but I’m not convinced it is the best approach any more 😉

Yeah, that was my feedback there - “visibility” is only one paradigm for the general problem of “validating dependencies”

Yeah, that was my feedback there - “visibility” is only one paradigm for the general problem of “validating dependencies”

Cool. I think that this could benefit from tying in at the FamilyAddress layer, so it effectively hides targets from the rule graph altogether, in some fashion.. unsure how it would work though.

we have an API already for validating -- whether it's too low-level is plausible

I didn’t find it was applied consistently the way I was counting on. Not sure if that was bug, or otherwise, but too late at some points. And for these things, I think they need to work at an even deeper level.

I’m referring to a simple function that receives a set of deps (and some context, such as config files) and returns a list of the deps that are disallowed, and some text explaining why.

I’m referring to a simple function that receives a set of deps (and some context, such as config files) and returns a list of the deps that are disallowed, and some text explaining why.

reminder that that already exists, and is used internally. whether it is shaped the right way for the external API is the question

Anyway, this isn’t the thread to be getting into designs

all done, thanks 😃