Add deviceAuthorization field to OAuthFlows object (OpenAPI 3.2.0) #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Implements the new
deviceAuthorization
field for theOpenApiOAuthFlows
object as defined in the OpenAPI 3.2.0 specification.Changes
Core Implementation
DeviceAuthorization
property toOpenApiOAuthFlows
class for configuring the OAuth Device Authorization flowDeviceAuthorization
constant toOpenApiConstants
for consistent field namingDeviceAuthorization
propertySerialization
The implementation handles version-specific serialization:
OpenAPI 3.2+: Serializes as a standard field
OpenAPI 3.1 and 3.0: Serializes as an extension for backward compatibility
Deserialization
deviceAuthorization
as a standard fieldx-oai-deviceAuthorization
extension and populate theDeviceAuthorization
propertyThis approach follows the same pattern used for other OpenAPI 3.2-specific fields like
$self
inOpenApiDocument
.Testing
Added comprehensive serialization tests covering:
All existing tests continue to pass (904 + 331 + 54 tests).
API Changes
Updated the public API export with:
OpenApiConstants.DeviceAuthorization
constantOpenApiOAuthFlows.DeviceAuthorization
propertyFixes #[issue number]
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
example.org926f4f21-88e7-4dc5-bf88-6c529bb77844
/usr/share/dotnet/dotnet exec --runtimeconfig /home/REDACTED/work/OpenAPI.NET/OpenAPI.NET/test/Microsoft.OpenApi.Hidi.Tests/bin/Debug/net8.0/Microsoft.OpenApi.Hidi.Tests.runtimeconfig.json --depsfile /home/REDACTED/work/OpenAPI.NET/OpenAPI.NET/test/Microsoft.OpenApi.Hidi.Tests/bin/Debug/net8.0/Microsoft.OpenApi.Hidi.Tests.deps.json /home/REDACTED/work/OpenAPI.NET/OpenAPI.NET/test/Microsoft.OpenApi.Hidi.Tests/bin/Debug/net8.0/testhost.dll --port 36503 --endpoint 127.0.0.1:036503 --role client --parentprocessid 23628 --telemetryoptedin false
(dns block)https://api.github.com/repos/BinkyLabs/BinkyLabs%2FOpenAPI.NET/languages
/home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js
(http block)If you need me to access, download, or install something from one of these locations, you can either:
Original prompt
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.