Currently, in order to override WarningRegistry you need to create a json file with an empty list and load that into WarningRegistry as documented in the README.
This means that any tooling that integrates this library cannot be stateless, it must either create temporary files or have a permanent place to store the registry.
Is there any appetite for providing an in-memory only variant of WarningRegistry that a consumer of this library can use to inject warnings scoped to the lifetime of the validator instance without managing temporary files?
Currently, in order to override
WarningRegistryyou need to create a json file with an empty list and load that intoWarningRegistryas documented in the README.This means that any tooling that integrates this library cannot be stateless, it must either create temporary files or have a permanent place to store the registry.
Is there any appetite for providing an in-memory only variant of WarningRegistry that a consumer of this library can use to inject warnings scoped to the lifetime of the validator instance without managing temporary files?