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

508 fixes #1155

Closed
Closed

Conversation

bdkosher
Copy link
Contributor

Addresses #1021 mostly by adding label tags, generating unique element ids as needed.

In the process, moved the label text that gets set in the ___ContentTypeView.js files to the respective handlebar templates; the text was static as far as I could tell.

There are additional minor 508 improvements that can be made with the tables (scope tags, header attributes)

Addresses swagger-api#1021 mostly by adding label tags, generating unique element
ids as needed.

In the process, moved the label text that gets set in the
*ContentTypeView.js files to the respective handlebar templates; the
text was static as far as I could tell.
@fehguy
Copy link
Contributor

fehguy commented Apr 14, 2015

@mohsen1 is this good to merge?

@fehguy fehguy added this to the v2.1 milestone Apr 14, 2015
@mohsen1
Copy link
Contributor

mohsen1 commented Apr 14, 2015

I don't exactly understand why we're doing this but if it's necessary to have unique identifiers it works for me.

@bdkosher
Copy link
Contributor Author

The ids have to be unique per the HTML specification--and the label tags which reference them are there primarily to appease US Federal Government agencies wanting to use Swagger UI.

@fehguy
Copy link
Contributor

fehguy commented May 8, 2015

Hi, it looks like we have some merge issues. Can you please rebase?

fehguy and others added 18 commits May 8, 2015 12:45
add jshint to gulp..lint and dist
Addresses swagger-api#1021 mostly by adding label tags, generating unique element
ids as needed.

In the process, moved the label text that gets set in the
*ContentTypeView.js files to the respective handlebar templates; the
text was static as far as I could tell.
Current code defaults to http protocol, but when package is installed in a https environment, the default validator should be securely available.
Addresses swagger-api#1021 mostly by adding label tags, generating unique element
ids as needed.

In the process, moved the label text that gets set in the
*ContentTypeView.js files to the respective handlebar templates; the
text was static as far as I could tell.
Using addApiKeyAuthorization function, needs to be done after swaggerUi is loaded, otherwise calling ``window.swaggerUi.api.clientAuthorizations.add`` will fail, and the authorization headers will not be aded.
mohsen1 and others added 15 commits May 8, 2015 16:54
…her/swagger-ui into develop_2.0-508_compliance

Conflicts:
	.gitattributes
	README.md
	dist/swagger-ui.js
	dist/swagger-ui.min.js
Addresses swagger-api#1021 mostly by adding label tags, generating unique element
ids as needed.

In the process, moved the label text that gets set in the
*ContentTypeView.js files to the respective handlebar templates; the
text was static as far as I could tell.
Using addApiKeyAuthorization function, needs to be done after swaggerUi is loaded, otherwise calling ``window.swaggerUi.api.clientAuthorizations.add`` will fail, and the authorization headers will not be aded.
…her/swagger-ui into develop_2.0-508_compliance

Conflicts:
	.gitattributes
	dist/swagger-ui.js
	dist/swagger-ui.min.js
	src/main/template/param.handlebars
	src/main/template/param_list.handlebars
	src/main/template/param_required.handlebars
@bdkosher
Copy link
Contributor Author

bdkosher commented May 9, 2015

Merge conflicts are gone, but dist/index.html isn't rendering successfully for me ("Uncaught TypeError: undefined is not a function" JS error). Investigating.

@bdkosher
Copy link
Contributor Author

After acknowledging how terribly I've screwed up my branch through my git naivete and witnessing the reemergence of merge conflicts, I thought I'd start over: reapply the 508 fixes on top of a fresh copy of the develop_2.0 branch HEAD and make a new pull request.

But before I even apply any changes, I find I'm still getting that JS error on render. Please tell me it's not just me with this problem.

@bdkosher
Copy link
Contributor Author

Please close this one that I've botched. I've submitted a new PR: #1291

@fehguy
Copy link
Contributor

fehguy commented May 15, 2015

sure thing

@fehguy fehguy closed this May 15, 2015
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

Successfully merging this pull request may close these issues.

8 participants