Fix missing limit parameter in STWFSA backend #718
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.








I noticed that if a STWFSA project configuration did not set the
limitparamter, the operations based on suggest functionality (CLI commands suggest, eval, index...) were crashing:The default
limitparameter was not obtainable fromAnnifBackend.DEFAULT_PARAMETERS, becauseStwfsaBackendclass defined its ownDEFAULT_PARAMETERSfield (without the limit parameter), but not adefault_params()method. Other backends having their ownDEFAULT_PARAMETERSfield had that method to include theAnnifBackend.DEFAULT_PARAMETERSin the parameters.I changed the
AnnifBackend.default_params()method to include bothDEFAULT_PARAMETERSfromAnnifBackend(base) class and from the instances of the concrete backend (derived) classes, like most backends were already doing. This way there is no need to duplicate the method in so many backend classes.In the fasttext backend the
default_params()method includes alsoDEFAULT_PARAMETERSfrommixins.ChunkingBackend, so it is needed to be retained to override the newAnnifBackend.default_params()method.