Error reporting for diagnostics#98
Conversation
|
@christianbpedersen can you please rebase this branch off |
09f6662 to
6949df5
Compare
|
I've rebased off current master and will look into tests, @Lordnibbler. |
|
@pitbulk, @luisvm, @Lordnibbler, rebased and tests added. |
|
Oops, look like I missed two cases. Adding now... |
|
@pwnetrationguru can you please remove the version bump from this branch? |
There was a problem hiding this comment.
@pwnetrationguru as per @Lordnibbler, could you please remove the version bump?
|
@pwnetrationguru , we need that you remove version bump, also we have the #147 that includes a new error, can you mix this PR (branch issuer) with your code and add its test? |
|
hey all, yep, i'll plan on updating this PR tomorrow! 👍 |
|
@Lordnibbler, @luisvm and @pitbulk, version bump removed, test added, should be GTG 🐥 |
|
Oops, looking at #147 now and will add that error |
|
@Lordnibbler, @luisvm and @pitbulk, re #147. I think the best approach is merge this PR into master and then comment on #147 to add the errors to Otherwise, I'm merging in changes from a PR that hasn't been merged into master yet,etc. Thoughts? |
|
@pwnetrationguru You can download the https://github.com/onelogin/ruby-saml/pull/147.patch do a: and handle with the error issue, then you can close the #147 referencing this PR, then merge this PR and at the end, delete the issuer branch |
|
That doesn't seem to follow
|
|
👍, id recommend @pwnetrationguru's steps for git but @pitbulk's will also work |
Error reporting for diagnostics
Status
READY
Description
This adds some error output.
Todos
Deploy Notes
Steps to Test or Reproduce
bundle exec rakeImpacted Areas in Application