-
Notifications
You must be signed in to change notification settings - Fork 715
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
smarty should be PSR-0 compatible for autoloading #15
Comments
exactly. |
Looking forward to that. |
👍 |
or PSR-4 👍 |
@hlohaus PSR-4 would also work ! |
PSR-0 autoloading is deprecated. So we will look into PSR-4 compatibility. |
ok |
PSR-4 ? seriously ? |
PSR-0 works for everything that does not use namespaces, but can be made to conform to a specific file layout. PSR-4 requires namespaces. Smarty doesn't use namespaces. So PSR-4 isn't available. Switching Smarty to namespaces will be an incompatible change, which should be released as a new major version, i.e. Smarty 4. |
+1 with @SvenRtbg |
Thats why i suggested plain PSR-0 |
I agree that PSR-0 looks for now to be the better solution. But this also requires changes in the folder structure and the renaming of some classes. This will create some backward compatibility issues. I have done it in my local 3.2 version. |
Hi, |
@pm-j Smarty provides it's own autoloader in addition to the Composer definition. Have you considered using it? |
@uwetews What is the current target date for 3.2 with namespaces? |
Smarty 3.2 cannot have namespaces because that would be an incompatible change. |
Any updates on getting into PSR-4 ? |
PSR-4 requires namespacing, this is best left to Smarty 3.2. |
3yrs down the line , any update on this ? |
The autoloading used with Smarty causes troubles with AspectMock. Could you please conform to PSR-0 for now, and then do PSR-4 in a major release? Thank you for all the hard work. |
If AspectMock have issues with standard autoloading schemes, raise it with that AspectMock thing. |
It does not appear to me that Smarty uses standard autoloading. If I am wrong, please correct me. But, I can think of three nonstandard things right now. |
It does, since December 2018. |
Shouldn't be this issue closed? |
Old issue- waiting for PSR 4 support |
release-2.0.2 merge to master
No description provided.
The text was updated successfully, but these errors were encountered: