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

[Synapse] Duplicate definition names #11856

Closed
jianghaolu opened this issue Nov 30, 2020 · 2 comments
Closed

[Synapse] Duplicate definition names #11856

jianghaolu opened this issue Nov 30, 2020 · 2 comments
Labels
Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@jianghaolu
Copy link
Contributor

In https://github.com/Azure/azure-rest-api-specs/blob/master/specification/synapse/data-plane/Microsoft.Synapse/preview/2019-06-01-preview/entityTypes/Trigger.json#L338

    "BlobEventTypes": {
      "type": "array",
      "items": {
        "type": "string",
        "enum": [
          "Microsoft.Storage.BlobCreated",
          "Microsoft.Storage.BlobDeleted"
        ],
        "x-ms-enum": {
          "name": "BlobEventTypes",
          "modelAsString": true
        }
      },
      "description": "Blob event types."
    },

The Enum name is defined as BlobEventTypes, but the top level schema name is also defined as BlobEventTypes. We need to rename either one to resolve the conflict in AutoRest.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Nov 30, 2020
@yungezz yungezz assigned idear1203 and unassigned yungezz Dec 8, 2020
@yungezz yungezz added the Service Attention Workflow: This issue is responsible by Azure service team. label Dec 8, 2020
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 8, 2020
@yungezz
Copy link
Member

yungezz commented Dec 8, 2020

hi @idear1203 could you pls have a look at the issue?

@idear1203
Copy link
Contributor

Fixed in #11864

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants