Ash Berlin-Taylor
Ash Berlin-Taylor
Hang on. With the TI history, I'm not sure we want to _ever_ delete TIs. Is this just a wording, or are we actually issuing a delete request on the...
-1. We should never delete TIs and TIH. This shouldn't even be a feature in the API!
I guess it's up to users if they want to do it, but we should probably make it 100% clear it will delete all history and audit records of the...
> We are bound to need at least one separate package if we want to entirely separate dependencies. For example, the WeightRule enum is fundamentally a user-facing type that should...
> * Should the Providers with executors be separated into providers to that they can be included on Server side? > > > Yes In my head, separate providers and...
> * Testing strategy? How to test package combinations efficiently > > > There should not be combinations. All packages should have the same version and should be released together...
Because this discussion has gone a down a different path to we first imagined mostly. We'll get something to the dev list "shortly"
I think we know what we are doing here and have a pattern to follow. Closing this issue.
(Yes, this def needs a news fragment, and likely a rule in our Ruff checks)
cc @uranusjr @Lee-W (I think you are working on ruff rules)