-
-
Notifications
You must be signed in to change notification settings - Fork 601
Documentation is incorrect / refers to changes not yet in dev-master #125
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
Comments
Hello @gramorris, thanks for the report! The dev-master is current part of a refactor to make a new major version, It's not advised to use it yet! @lcobucci please correct me if I'm wrong! |
@renatomefi thanks, we didn't see anywhere where it says it's not advised to use it, it's worked and is working fine for us. I just felt it was worth pointing out that the documentation on the project homepage is incorrect as per the current commit. |
Even though |
@schnittstabil do you mean tagging me or the issue author? :) Thanks for making it clear though! Also agree in keeping the documentation up to date, I'm just worried the author was using master branch and it can be unsafe for now! |
We're getting in to a discussion of semantics so I'll just say that what we assumed was the risks associated with using a dev-master branch, we were happy to proceed on that basis. There's no need to be worried on our behalf. As the documentation for the dev-master is on the project homepage and is incorrect/inconsistent I felt it worth pointing out, that was all I was doing. |
You did right! Thanks for it! |
WOW! Guys you're just awesome! Basically you're all right 😂 @gramorris thanks for pointing out about the doc, I'll fix it. @gramorris is good to know that we have some early users, but mind the changes. I'm working on the validation refactor and that is going to be merged soon (https://github.com/lcobucci/jwt/tree/refactor/validator-extraction). |
Thanks @lcobucci , appreciate the work on the library, we've not found any issues with the functionality so far 👍 |
On lcobucci/jwt#119 we changed unrelated things on the documentation and this fixes lcobucci/jwt#125.
We're running latest dev-master version (972cfe0) and as part of the update changed the Configuration method names to issuedBy & canOnlyBeUsedBy etc.
The documentation shows the same changes for ValidationData however the ValidationData code is still using the old methods setIssuer and setAudience - using issuedBy & canOnlyBeUsedBy results in a "Call to undefined method Lcobucci\JWT\ValidationData::issuedBy()"
The text was updated successfully, but these errors were encountered: