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

Add a way to document security properties from the view #58

Merged
merged 2 commits into from
Jan 25, 2017

Conversation

gabisurita
Copy link
Collaborator

Related to #34

This may not be the best solution, but at least is a way of documenting security properties from the view. It uses the same interface for op_ids and tags.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling f7a58c2 on view-security into 6b3d731 on master.

3 similar comments
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling f7a58c2 on view-security into 6b3d731 on master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling f7a58c2 on view-security into 6b3d731 on master.

@coveralls
Copy link

coveralls commented Jan 25, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling f7a58c2 on view-security into 6b3d731 on master.

@gabisurita gabisurita merged commit 3e96d11 into master Jan 25, 2017
@gabisurita gabisurita deleted the view-security branch January 25, 2017 16:08
(e.g GET) and returns an operation Id that should be unique.
:param default_security:
Provide a default list or a callable that takes a cornice
service and the method name (e.g GET) and returns a list of Swagger
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

µnit: e.g.

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.

3 participants