-
Notifications
You must be signed in to change notification settings - Fork 12
Refactor Azure Functions to use declarative REST services instead of manual routing #1099
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Cherry pick to beta success |
Cherry pick to beta success |
Cherry pick to beta failed, 1 conflicted file in commit 18312f7
|
Manual cherry pick to beta success |
Cherry pick to beta failed, 1 conflicted file in commit 37a0195
|
Manual cherry pick to beta success |
Cherry pick to beta success |
Cherry pick to beta success |
Cherry pick to beta success |
Cherry pick to beta failed, 1 conflicted file in commit 6e7b7ed
|
Manual cherry pick to beta success |
Cherry pick to beta success |
Cherry pick to beta failed, 0 conflicted files in commit 0689c97 (warning: no changes merged) |
Manual cherry pick to beta success |
Cherry pick to beta success |
Cherry pick to beta success |
…is needed for decimals represented as strings.
Cherry pick to beta success |
…/DotNetClasses into AzureRestControllers
Cherry pick to beta success |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We decided to create a separate PR to address the two existing ways of accessing HttpContext — via GetHttpContext() and the base class HttpContext — since the latter is not reliable in Azure environments and could lead to fragile or broken scenarios.
Additionally, we will remove the duplicate StringConverter implementation, since it already exists in GxCollections.cs.
Issue:201688