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
Once we have the ability to modify types in TypeSpec ([TCGC] Add @alternateType to change the type of a property (with scope) · Issue #1757 · Azure/typespec-azure), start with isolating the change to just the client.tsp scoped to C++ and verify the generated code works as expected. In the future, if it can be generally accepted across all language SDKs without impacting customers of the SDKs, we can consider moving it to the main routes.tsp common across all languages.
ahsonkhan
changed the title
Use the alternateType decorator toe change the acceptDateTime field from string to offsetDateTime so it is emitted as an RFC 1123 Azure.Core.DateTime
Use the alternateType decorator to change the acceptDateTime field from string to offsetDateTime so it is emitted as an RFC 1123 Azure.Core.DateTime
Jan 13, 2025
ahsonkhan
changed the title
Use the alternateType decorator to change the acceptDateTime field from string to offsetDateTime so it is emitted as an RFC 1123 Azure.Core.DateTime
Use the alternateType decorator to change the acceptDateTime field from string to utcDateTime so it is emitted as an RFC 1123 Azure::DateTime
Jan 14, 2025
https://github.com/Azure/azure-rest-api-specs/blob/9cda51602860201954415dab20bdcbcf389c7da9/specification/appconfiguration/AppConfiguration/routes.tsp#L684-L685
azure-sdk-for-cpp/sdk/appconfiguration/azure-data-appconfiguration/inc/azure/data/appconfiguration/configuration_client_options.hpp
Lines 171 to 180 in 53a74b0
Once we have the ability to modify types in TypeSpec ([TCGC] Add @alternateType to change the type of a property (with scope) · Issue #1757 · Azure/typespec-azure), start with isolating the change to just the client.tsp scoped to C++ and verify the generated code works as expected. In the future, if it can be generally accepted across all language SDKs without impacting customers of the SDKs, we can consider moving it to the main routes.tsp common across all languages.
The AppConfig service officially only document RFC 1123 format support. Service ignores this header if the value is not in the right format:
https://learn.microsoft.com/en-us/azure/azure-app-configuration/rest-api-labels?pivots=v23-10#time-based-access
From the service team, it is safe to assume that the only valid supported format here is an RFC 1123 date time (from the spec linked in the API docs HTTP Framework for Time-Based Access to Resource States)?
The text was updated successfully, but these errors were encountered: