Skip to content

docs/add specific errors #44

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

Merged
merged 2 commits into from
Feb 11, 2015
Merged

docs/add specific errors #44

merged 2 commits into from
Feb 11, 2015

Conversation

DirectXMan12
Copy link
Member

This adds specific GSSAPI errors to the documentation, as per #11

@DirectXMan12
Copy link
Member Author

If someone could double check that this looks good rendered as well, that would be great

@DirectXMan12 DirectXMan12 added this to the 1.1.0 milestone Feb 10, 2015
@frozencemetery
Copy link
Member

This looks good when rendered to me.

Now that we have specific errors (found in `gssapi.raw.exceptions`),
we should document which errors can be thrown.

This commit does so for the low-level API.  In the case where no
errors were documented, the only error documented was the generic
GSSError, otherwise, GSSError was removed, and the specific listed
errors were added (except in the case where GSS_S_FAILURE is
specifically listed, in which case so is GSSError).

Note that non-RFC extensions did not have specific errors documented,
since they do not have a standardized list of specific errors.

Part of #11
Now that we have specific errors (found in `gssapi.raw.exceptions`),
we should document which errors can be thrown.

This commit does so for the high-level API.

Closes #11
@frozencemetery frozencemetery force-pushed the docs/add-specific-errors branch from d27eb81 to e14d5a9 Compare February 11, 2015 14:34
@frozencemetery frozencemetery merged commit e14d5a9 into master Feb 11, 2015
@frozencemetery
Copy link
Member

Rebased and merged.

@frozencemetery frozencemetery deleted the docs/add-specific-errors branch February 11, 2015 14:47
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.

2 participants