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

[2.0] Operation expansion doesn't work with paths containing a dot #735

Closed
webron opened this issue Nov 21, 2014 · 3 comments
Closed

[2.0] Operation expansion doesn't work with paths containing a dot #735

webron opened this issue Nov 21, 2014 · 3 comments

Comments

@webron
Copy link
Contributor

webron commented Nov 21, 2014

Following the question on SO - http://stackoverflow.com/questions/27046475/swagger-ui-2-1-stuck-fetching-resource-list - there's the UI will not expand if the path is /match.json when clicking on it. The same would apply for /match.hello. Clicking on Expand Operations will show the operation.

The SO question's sample has an additional issue with it that doesn't allow it to render properly, but once fixed, the issue is clear.

Sample spec to reproduce:

{
    "swagger": "2.0",
    "info": {
        "title": "TITLE",
        "description": "BLAH, BLAH, BLAH, ETC",
        "version": "1.0b"
    },
    "host": "api.example.com",
    "schemes": [
        "http"
    ],
    "basePath": "/v1",
    "produces": [
        "application/json"
    ],
    "paths": {
        "/match.json": {
            "get": {
                "description": "Used for getting data about a match",
                "parameters": [
                    {
                        "name": "id",
                        "in": "query",
                        "description": "The match ID of from a game",
                        "required": true,
                        "type": "integer",
                        "format": "int32"
                    },
                    {
                        "name": "key",
                        "in": "query",
                        "description": "API key used for authentication.",
                        "required": true,
                        "type": "string"
                    }
                ],
                "responses": {
                    "200": {
                        "description": "Returns match data",
                        "schema": {
                            "type": "string"
                        }
                    }
                }
            }
        }
    }
}
@AzureFlow
Copy link

I would love to see this get fixed.

@fehguy
Copy link
Contributor

fehguy commented Dec 3, 2014

This issue is tracking the general problem:

#726

fehguy added a commit that referenced this issue Dec 3, 2014
@fehguy
Copy link
Contributor

fehguy commented Dec 3, 2014

a fix specific to the "." is applied to the develop branch.

@fehguy fehguy closed this as completed Dec 3, 2014
fehguy added a commit to swagger-api/swagger-js that referenced this issue Dec 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants