AndrewSisley

I have started this work on branch `2619-self-field-kind`, switching to https://github.com/sourcenetwork/defradb/issues/2625 as it will make doing this ticket easier.

Note, I have a (early) WIP branch of name 2493-field-kind-schema-vs-col, breaking https://github.com/sourcenetwork/defradb/issues/2619 out of this task and working on that first.

Had a thought - if/when implementing the ds.Get call chain, do it in a feature-agnostic way that allows fetcher to use ds.Get when it can

> able to set a flag Ordered to make sub tests run in the given order Why would you want this? Why should we permit this? > we can add...

> Some people (including me) use more often IDE Ah true, we definitely shouldn't make that painful, might be well worth adding a couple of easily settable props like you...

> Though this will certainly increase overall robustness, but also significantly increase time to run all the tests. It really shouldn't, it will just be another item in the CI...

> These tests will certainly make sure the indexes produce correct results (the same results as without indexes), but we still want to have dedicated tests to make sure indexes...

Note before disappearing for the weekend and potentially getting caught up in bug bashing and normal dev next week: I am closing on an initial plan for this in my...

I've updated the issue description with my thoughts from during the cooldown, posting in this comment too to preserve the history Write up # Proactive tests At the moment all...

Note: This is currently under discussion in the `dev-db.ACP` discord thread: https://discord.com/channels/427944769851752448/1200142876307374100 ---- Discussion summary: Within a single node, within the context of a user request (not limited to GQL...