| Carsten Hammer thanks a lot, good to see a sensible use case! The reason PojoIndexedTypeIdentifier is not exposed (nor documented) is that it's a temporary implementation detail: the way TypeIdentifier instances are produced will need to use a stateful registry so using a static helper method will not be possible. We can re-introduce the legacy Work constructor, but we'll need to remove it shortly: this is one step of a larger refactoring, so you might as well temporarily use PojoIndexedTypeIdentifier directly if all you needed was a temporary solution. Clearly the better solution would be to provide a proper API for mass deletion. |
