Answer the question
In order to leave comments, you need to log in
Which Laravel engine to use?
I'm slowly delving into Laravel, the documentation certainly helps, but sometimes I want to hear the thoughts of real people. There is a need to implement a certain system of components. Components can be registered and then somehow used. The question is how best to implement the storage of a list of these components so that it is available throughout the entire life cycle of the application. Something like Components::register(...config...) comes to mind to register a component and $app->components to get a list of registered components. How is it better to implement, what to use? Kick in the right direction and I'll go read the docks)
Answer the question
In order to leave comments, you need to log in
It is not completely clear what the author understands by the word “component”, but, probably, the capabilities of the service container will be enough for him, about which he will go and read in the documentation. And for a snack, you can read about Package Development .
Plugin systems, as in different CMS, are not in Laravel, because it is not a CMS. Everyone is free to invent their own, based on the possibilities described above.
I didn’t quite understand your question, but maybe containers will help you?)
The description is, of course, very vague and using terminology that is somehow perpendicular to Laravel ... There is a container - all your "components" are registered there, they are also available in a "list" from "anywhere" and "throughout the entire application cycle". There are service providers, which in essence and including are the mechanism for registering your "components" in the container (and, as a result, the application). And there are a bunch of other features that are sure to replace elements of your components if you understand Laravel's internals and start thinking about its architecture.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question