Merging HTTP feature branch #1648
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updating build to ensure future feature branches work as expected
fabiocav
force-pushed
the
feature/enhanced-http
branch
from
07730c6 to
69398e4
Compare
satvu
reviewed
Jun 19, 2023
| { | ||
| public class HttpProxyTrigger | ||
| { | ||
| [Function(nameof(HttpProxyTrigger))] |
There was a problem hiding this comment.
Outside of scope for this PR, but do we want to make a different sample app for the aspnet integration examples? Would make sense since the wire up is different + we don't want to interfere with the current http model being used in this app.
satvu
approved these changes
Jun 19, 2023
brettsam
approved these changes
Jun 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue describing the changes in this PR
resolves #1387
Pull request checklist
release_notes.md