Comments (8)
Ocramius,
That's even more stupid.
So basically you let them use an abandoned old version.
Shame on you.
from jwt.
👍
from jwt.
PHP 7 is not release yet.
As per the PHP website:
"THIS IS A DEVELOPMENT PREVIEW - DO NOT USE IT IN PRODUCTION!"
Therefore JWT should not be written in PHP7 yet !
from jwt.
It's going to be stable in 2 weeks, so that is not a problem. Not every new
software bit needs to be developed against stable software only.
On Oct 31, 2015 09:12, "udf2457" [email protected] wrote:
PHP 7 is not release yet.
As per the PHP website:
"THIS IS A DEVELOPMENT PREVIEW - DO NOT USE IT IN PRODUCTION!"Therefore JWT should not be written in PHP7 yet !
—
Reply to this email directly or view it on GitHub
#51 (comment).
from jwt.
Ocramius,
Please. Be sensible !
PHP7 might be "stable in 2 weeks" .... but how many people, honestly, are going to be bleeding-edge day zero adopters.
How many people have yet to even make the transition from PHP 5.5 to PHP 5.6 ? And that's only a minor release.
I think it is far, far too early for you to say "who cares about <7 users ...." ... maybe in 12/24 months.
from jwt.
They can still use the previous version of the lib: that's why major
versions exist ;-)
On Oct 31, 2015 13:27, "udf2457" [email protected] wrote:
Ocramius,
Please. Be sensible !
PHP7 might be "stable in 2 weeks" .... but how many people, honestly, are
going to be bleeding-edge day zero adopters.How many people have yet to even make the transition from PHP 5.5 to PHP
5.6 ? And that's only a minor release.I think it is far, far too early for you to say "who cares about <7 users
...." ... maybe in 12/24 months.—
Reply to this email directly or view it on GitHub
#51 (comment).
from jwt.
Who ever said old versions are abandoned? That is not how it works, do not
worry. There is bug/security support for (some) older versions of pretty
much every lib.
See ZendFramework for example: v1.* is still maintained and patched for
bugs/security issues since 3 years after 2.* came out.
On Oct 31, 2015 13:30, "udf2457" [email protected] wrote:
Ocramius,
That's even more stupid.
So basically you let them use an abandoned old version.
Shame on you.
—
Reply to this email directly or view it on GitHub
#51 (comment).
from jwt.
@udf2457 the v3.x is fully working and we have dozens of BC-break ideas, that's why we're going to make a v4.x (but the v3.x will be maintained).
With that we can have PHP 5.5+ folks using v3.x (and helping to make it even better - respecting the BC) and PHP 7+ folks using the v4.x new API.
The v4.x won't be released in less than 14 days.
We also have (until now) two features that can be implemented for a v3.1 (#29 and #49).
from jwt.
Related Issues (20)
- Uncaught Error: Class "Lcobucci\JWT\JwtFacade" not found HOT 1
- error Undefined method 'claims'. HOT 1
- Suggestion: Make Parser methods public HOT 6
- It was not possible to parse your key, reason: error:0480006C:PEM routines::no start line HOT 2
- Getting error * error:0906D06C:PEM routines:PEM_read_bio:no start line HOT 3
- Class "Lcobucci\JWT\Validation\Constraint\LooseValidAt" not found HOT 4
- Builder#withClaim() is meant to be used for non-registered claims, check the documentation on how to set claim \"sub\"" HOT 3
- Wrong timezone while parsing jet HOT 1
- Uncaught Error: Class "Lcobucci\JWT\JwtFacade" not found in version 5.1 HOT 2
- Impossible to parse private key HOT 2
- JWT token signature is not validated when parsing from configuration HOT 3
- Failed to parse token using the decoder key ECDSA with Sha384 HOT 4
- Class Lcobucci\JWT\Signer\Key\InMemory may not inherit from final class HOT 8
- Add claims() function to token interface HOT 4
- Remove UnifyAudience ClaimFormatter HOT 5
- It was not possible to parse your key, reason: error:1E08010C:DECODER routines::unsupported HOT 2
- No change to composer.json, but a composer update result in "Key provided is shorter than 256 bits, only 240 bits provided" error HOT 5
- Deprecated empty key HOT 2
- "Key cannot be empty" error HOT 6
- Broken upgrade path from 3.4 to 4.0 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jwt.