Error: [ngRepeat:dupes] Duplicates in a repeater are not allowed (Fix) about angular-swagger-ui

[mathieuales]

Hi !
This should not be the way to fix the issue ...
Do you mind sending your swagger descriptor as i can't reproduce using my samples?

[mathieuales]

Can't reproduce the issue with your file on the demo: http://orange-opensource.github.io/angular-swagger-ui/
Could you please show how you use the component ?

[bodinegl]

actually I am having the very same issue but only when I use the swagger-ui directive in a partial as part of a singe page app. if I put it in the index.html page like your example it works fine.

[mathieuales]

should be fixed in 0.2.2, can you confirm ?

[bodinegl]

0.2.2 did fix the ngRepeat:dupes error but now I have a new issue. every
time I hit the "open/hide", "list operations", "expand operations" buttons
I get two additional duplicate operations in the list. (see attached).
there should only be one. I also see the "error{}" now, which use to be
verify.

thanks
--greg

swagger doc:

{"info": {"version": "1.0.0", "contact": {"name":
"[email protected]"}, "description": "#### base connectors return the
contents of a file\n", "license": {"url":
"http://www.test.com/legal/license-agreements.aspx", "name": "Test
Inc."}, "title": "Base - Cloud Connectors", "copyright": "2015 Test
Inc. ALL RIGHTS RESERVED"}, "paths": {"/base": {"get": {"description":
"base connector description for get verb", "tags": ["base"],
"summary": "base connector summary for get verb", "responses": {"200":
{"description": "successful operation"}}, "produces":
["application/json"]}}}, "schemes": ["http"], "produces":
["application/json"], "basePath": "/connector", "tags": [{"name":
"base", "description": "base connector"}], "host": "localhost:8080",
"swagger": "2.0"}

[image: Inline images 1]

when I click the "error {}" I see the following:

[{"level":"error","message":"Can't read from file
http://localhost:8080/connectors/base"}]

but if I go to that link directly I get the swagger doc back like above.

On 21 August 2015 at 09:13, Mathieu Alès [email protected] wrote:

should be fixed in 0.2.2, can you confirm ?

—
Reply to this email directly or view it on GitHub
#17 (comment)
.

[mathieuales]

I finally reproduced the issue when using 'ngRoute'. If you do so, you can fix the issue by adding reloadOnSearch = false in your route configuration