Open logogin opened 6 years ago
Any chance to get this merged?
Could you elaborate a bit on the use-case of when you'd load custom dictionaries from locations other than the Java classpath? Just trying to understand the underlying use-case. Thanks.
Thanks for the response! The are couple of use-cases:
It is also, in general, a very trivial change which is backwards-compatible and does not affect library API. The ResourceResolver
interface is already there, it is just hardcoded to resolve always from classpath.
This small change adds ability to set custom
ResourceResolver
viaBuilder
. Custom resolver will allow loading dictionaries from locations other than Java classpath.