[WIP] Recognize vendor extensions for primitives
See original GitHub issueI recently submitted Swashbuckle PR #776. I’d appreciate any feedback.
Basically, if AutoRest recognized the x-nullable
and x-type
(or x-type-dotnet
) vendor extensions I’m proposing, should they (or something similar) be enabled, then the AutoRest generated C# proxy could remove the type impedance mismatch we have today - whether or not a type is nullable would not have to be conflated with whether or not a type is required, and secondly the original C# type could be preserved for C# clients. This should cover use in parameters, request / response types, composite types, arrays etc.
Issue Analytics
- State:
- Created 7 years ago
- Comments:17 (10 by maintainers)
Top Results From Across the Web
Use the Microsoft.Extensions.Primitives library - .NET
In this article. Change notifications; Instance-based functionality; Alternative static approach; String tokenizers, segments, and values ...
Read more >MIB concepts and design - IBM
All MIB modules are eventually extensions of the root module. All released MIB modules, from individual vendors, extend from the enterprises object defined...
Read more >WebGPU - W3C
Possibly identifying, for example, the adapter's vendor and general ... WebGPU implementations must not expose extension functionality; ...
Read more >3E Templates User Guide - Thomson Reuters Legal Solutions
Open the Primitives category in the Toolbox and drag the Assign activity ... Define the path to the Text-to-XML template (.dgt extension).
Read more >hughsie – Page 3 – Technical Blog of Richard Hughes
I've got a wip/hughsie/jcat branch on fwupd, and the same for lvfs-website ... bizarrely makes no mention of any kind of vendor ID...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am just about to implement
x-nullable
right now.@devigned @Azure/adx-autorest-contributors Thoughts about having AutoRest support
x-nullable
? From the discussion here it seems there is consensus that it will be standardized in OpenAPI at some point.x-nullable
would solve a bunch of issues:These are causing our team and others a bunch of pain. Solving it would eliminate nearly every case where we have to use
x-ms-external
in our specs today.