You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently both old (v2) and new (v3) Form Recognizer APIs have their model factory generation disabled in the autorest configuration file.
Ideally, we should be able to:
Reenable model factory generation for the new API.
Add the CodeGenModel("FormRecognizerModelFactory") attribute to the DocumentAnalysisModelFactory class. This will make all generated models to be put into the new factory.
Remove as many duplicates as we can from the manually written side of the DocumentAnalysisModelFactory class. We want to maximize the amount of generated code.
There's one issue with the approach above: the old FormRecognizerModelFactory already has a CodeGenType("FormRecognizerModelFactory") attribute. If we add the attribute to the new factory, autorest fails due to the duplicated keys. If we remove the attribute from the old factory, ApiCompat fails.
Removing this internal attribute from the old factory is not considered a breaking change, so we need to suppress this error somehow.
The text was updated successfully, but these errors were encountered:
Currently both old (v2) and new (v3) Form Recognizer APIs have their model factory generation disabled in the autorest configuration file.
Ideally, we should be able to:
CodeGenModel("FormRecognizerModelFactory")
attribute to theDocumentAnalysisModelFactory
class. This will make all generated models to be put into the new factory.DocumentAnalysisModelFactory
class. We want to maximize the amount of generated code.There's one issue with the approach above: the old
FormRecognizerModelFactory
already has aCodeGenType("FormRecognizerModelFactory")
attribute. If we add the attribute to the new factory, autorest fails due to the duplicated keys. If we remove the attribute from the old factory, ApiCompat fails.Removing this internal attribute from the old factory is not considered a breaking change, so we need to suppress this error somehow.
The text was updated successfully, but these errors were encountered: