Re: Negative patterns in cone mode

From: Rudy Rigot <rudy.rigot@gmail.com>
Date: Apr 8, 2023, 15:43 UTC
Message-ID: <CANaDLWJ4XSFUULc4PGen_trsyJ1_K1qoufisoxgpjCfMhoDjKQ@mail.gmail.com>
In-Reply-To: <GVXPR10MB8199D186532A7A285CCF1538B9939@GVXPR10MB8199.EURPRD10.PROD.OUTLOOK.COM>

Hi,

> I'm facing an issue with negative patterns in cone mode.
> I can't tell from the docs or git code if I misunderstand the
> usage, am trying something not supported, or if there is a
> bug.

My understanding so far, and I would appreciate if someone can correct me if I'm wrong, is that the point of cone mode is that there can't be negative patterns, and everything is a positive rule, so the match search can stop as soon as a positive rule is found.

My understanding has been that it was designed with the use case in mind of large mono-repos made of several independent applications, of which a given developer only needs a few. For instance, if I am an iOS developer, I will configure my sparse checkout to have the back-end code and the iOS code, but not the front-end code and the Android code.

I don't know if that's accurate because I'm not as well-versed
about it as I should be, so I would appreciate if someone could
correct my understanding. It is the chief reason we are
sticking with non-cone mode with our massive monolith at
Salesforce: it is not a mono-repo of independent applications,
but one massive monolith of which only a few (very large) files
are not needed for all devs.

Thanks in advance for anyone who may have insights.