Open adamcsillag opened 4 months ago
@adamcsillag thanks for pointing this out!
The API documentation is a little misleading in this case. It should be possible to specify custom match types, not just 100
and 99-82
.
The current implementation doesn't allow such values, so it should be improved to allow custom ranges as well.
Hi,
Is it possible to have custom fuzzy match types in a TranslationCostsPostEditingGenerateReportRequest? In NetRateSchemes it is possible to specify SuggestionMatch values, however there are only MatchType.Option_99_82 and MatchType.Option_81_60 fuzzy match types. On the UI It's possible to add custom match types: