Skip to content
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

feat(designer): Adding support for file parameters for Appservice and Api Management operations #4734

Merged
merged 3 commits into from Apr 30, 2024

Conversation

preetriti1
Copy link
Contributor

  • Please check if the PR fulfills these requirements
  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes/features)
  • Docs have been added / updated (for bug fixes / features)
  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
    Missing feature

  • What is the current behavior? (You can also link to an open issue here)
    swagger parameters containing file type parameters in http+swagger, apim and app service actions are totally skipped. fixes Error using API Management action with multipart/form-data request payload: "Failed to retrieve dynamic inputs" after switching to the new designer  #4611

  • What is the new behavior (if this is a feature change)?
    File type parameters are now recognized. Since we formed the above actions as a hybrid of manifest and swagger, so formdata is explicitly handled for manifest based operations now.

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

  • Please Include Screenshots or Videos of the intended change:

@preetriti1 preetriti1 merged commit 3ff85d7 into main Apr 30, 2024
11 checks passed
@preetriti1 preetriti1 deleted the priti/multipart branch April 30, 2024 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants