Multi-level discriminator handling improvements

[radhgupta]

This pull request refines the logic for handling multi-level discriminators in model constructor initialization within ModelProvider.cs. The changes ensure more accurate passing of discriminator parameters in complex inheritance scenarios, improving both correctness and maintainability.

Multi-level discriminator handling improvements

• Updated the logic to check whether the current model or base model uses a multi-level discriminator, ensuring the correct constructor is called and the appropriate discriminator value is passed in multi-level inheritance scenarios.
• Enhanced the handling of discriminator parameters: now, when initializing constructors, the code attempts to pass through the discriminator parameter from the base model if available, otherwise falls back to using the current model's discriminator value.
• Improved the logic in GetExpressionForCtor to correctly decide when to pass through the discriminator parameter or use the model's own discriminator value, based on whether the model is part of a multi-level discriminator hierarchy.

Constructor initialization logic

• Ensured that base constructor calls are properly made even when there are no base parameters, maintaining correct inheritance behavior.

[github-actions]

No changes needing a change description found.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/microsoft/typespec/@typespec/http@9119

npm i https://pkg.pr.new/microsoft/typespec/@typespec/http-client@9119

npm i https://pkg.pr.new/microsoft/typespec/@typespec/http-client-csharp@9119

commit: 4ad4a9c

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension