[formrecognizer] Arch board issues #11283
Description
- Consider renaming
form_file_streamandreceipt_file_streamto be more general likedatasince it accepts file-like object or bytes in memory [formrecognizer] rename input parameters #11518 - Update docstring type to match type hint for recognize input: Union[bytes, IO[bytes]]
- Update samples to take stream as input
- Update samples to show
confidenceonFormWord - Should the
get_clientmethod move toFormTrainingClient? Should we remove it altogether?
We will move the get_client method to FormTrainingClient - Reconsider naming around
CustomFormSubModel. We want people to understand what this is without having to look at documentation. Tracked in [form recognizer] renamemodelsproperty ofCustomFormModeltosubmodels#11389 - Also reconsider naming for
CustomFormModel.modelsattribute. Tracked in [form recognizer] renamemodelsproperty ofCustomFormModeltosubmodels#11389 - Should we enforce guid format for model_id? No [formrecognizer] model_id param validation #11569
- Reconsider having
use_training_labels=Falseas the default. Possibly make this a required param. Make use_training_labels positional required #11529 - Do we need to reconsider naming of
last_modified? This assumes it's mutable and it's not. Rename to completed_on and requested_on in the CustomFormModel #11592 - Is
receipt_localespecific enough to differentiate all receipt types? See this issue: [Design] Form Recognizer: Is Receipt-Locale specific enough to differentiate all receipt types azure-sdk-for-net#11912 and consider design for future (Note: receipt_locale won't be exposed in v2.0)