-
Notifications
You must be signed in to change notification settings - Fork 142
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
Fix psr4 autoload warning #322
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm sorry, but we can't just change a class name in it's defining file and not everywhere else it is located in the project.
i could not find any other file that uses |
So I have a useless trait causing issues... I will give a second look when I get a chance. Thank you for bringing this to my attention |
it might be an uncleaned commit after migration since |
It actually looks like you uncovered my indecisiveness in choosing inheritance over composition with traits... I think Renderable used to be a trait, but then I made it a class... investigating... |
I also moved the |
Hi thanks for the PR, but I still see this warning when running Class Khill\Lavacharts\Support\RenderableTrait located in ./vendor/khill/lavacharts/src/Support/Renderable.php does not comply with psr-4 autoloading standard. Skipping. |
Can you please tag a patch release to resolve this issue, thank you! cc @kevinkhill |
I forget to mention that I have Composer version 2 (moved to it because it's much faster), so this is an issue now not just a warning! |
@yaayes I believe he push the patch for version 4, I've tried it but seems there was a breaking changes and I could not find doc for it. for now probably wait in indefinite time |
awww, I don't like discouraging you and hearing "indefinite" I have 30 minutes right now, lets see if I can make something happen. |
Hi thankyl you @ChaerilM and @kevinkhill |
let me know if errors arise please! I didn't test anything, because I'm off to my paying job now 😄 |
Thanks @kevinkhill for taking the time to solve this. Very appreciated! |
Updated successfully without any warnings related to composer v2, and I can confirm that nothing break (at least in my application which use like four/five type of commons charts) |
Awesome, glad to hear that. 🤞🏻 All my hot glue and duct tape keeps 3.1 together until I eveeeeentually carve time for v4 |
composer gives warning while update. in some case, it does not add lavachart to autoloading due to this issue