Closed
Description
- Consider renaming
form_file_stream
andreceipt_file_stream
to be more general likedata
since 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
confidence
onFormWord
- Should the
get_client
method 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] renamemodels
property ofCustomFormModel
tosubmodels
#11389 - Also reconsider naming for
CustomFormModel.models
attribute. Tracked in [form recognizer] renamemodels
property ofCustomFormModel
tosubmodels
#11389 - Should we enforce guid format for model_id? No [formrecognizer] model_id param validation #11569
- Reconsider having
use_training_labels=False
as 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_locale
specific 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment