Is there any tooling or thoughts around reporting ...
# spicedb
c
Is there any tooling or thoughts around reporting on "cost" of a schema item to resolve (from the schema perspective, not necessarily in actual resolution reporting)? That is, longer graph paths take more to resolve than simple, short ones. For context, we are making load test plans and want to ensure that we are not concentrating on lower cost paths when we make our test scenarios.