Currently, both jieba and lindera rely on a shared configuration loading function via json.
While this works well in general, I'd like to make use of lindera's more extensive configuration options.
To enable this, I propose separating the loading configuration handling for jieba and lindera.
I’ve tried this approach locally, and it appears to work as expected.
I’m planning to open a pull request with this change, but before doing so, I wanted to ask if there are any concerns or considerations I should be aware of.
Currently, both jieba and lindera rely on a shared configuration loading function via json.
While this works well in general, I'd like to make use of lindera's more extensive configuration options.
To enable this, I propose separating the loading configuration handling for jieba and lindera.
I’ve tried this approach locally, and it appears to work as expected.
I’m planning to open a pull request with this change, but before doing so, I wanted to ask if there are any concerns or considerations I should be aware of.