microsoft / microsoft/PowerPlatformConnectors

[BUG] Power Automate Editor Import OpenAPI 3.0 - allOf not changed

Open
#2,067 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Description

Type of Connector

Custom Connector

Name of Connector

GitHub Gists

Describe the bug

I was able to successfully import the connector definition (after removing non-Gists-related definitions) from:
https://raw.githubusercontent.com/github/rest-api-description/main/descriptions/api.github.com/api.github.com.json
In the Swagger Editor, I can see that the definition has been downgraded to 2.0. However, the allOf keyword has still been included. So, I have two questions:

  1. Does the Editor saving without an error mean that the custom connector can be used with the allOf parameters?
  2. The paconn CLI validate command completes with warnings, but should these be fixed before submission as an Independent Publisher connector? (I may fix and submit anyways, as it is only two warnings)

image

Is this a security bug?

No, this is not a security bug

What is the severity of this bug?

Severity 3 - Minor issue

To Reproduce

Import OpenAPI definition that includes allOf keyword (I'm guessing this is similar for oneOf, anyOf, and not as well)

Expected behavior

Editor downgrade removes the need for allOf keyword

Environment summary

Install Method (e.g. pip, interactive script, apt-get, Docker, MSI, edge build)
CLI version (paconn --version)
OS version
Shell Type (e.g. bash, cmd.exe, Bash on Windows)

Additional context

None

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the OpenAPI definition linked in the issue and reproduce the import in the Swagger Editor, focusing on the OpenAPI 3.0 to 2.0 downgrade and its handling of allOf. Then run the paconn CLI validate command and compare the editor output and warnings with the expected behavior that unsupported composition keywords are handled before submission.

Written by the indexing model from the issue text.

Assessment

Tech stack
openapi
Domain
api, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.