🛠Creating our own custom service programatically 🛠

[@fiftystory]

Thanks a lot really informative ....

[@dineshshrivastava4597]

Nice Video, What is the Editor you used?

[@RajkumarDgupta]

atom

[@chipsybit8046]

You made an error in the drupalup_service.info.yml file at 1:24. look in your git repo, "type" and "description" is reversed. If you make a modul like in your video, the modul will not be shown in extend or not be able to enable via drush. edit: okay everythings fine, strangely i named the info file wrong.

[@Drupal-up]

Hi Chipsy Bit, in the video there is no problem in the .info.yml file. Yes it is indeed reversed in the repo ( github.com/drupal-up/drupalup_service/blob/master/drupalup_service.info.yml ), but the order does not matter. Also, you wrote that "If you make a module like in the video ..." but in the video, the order is "description first", so I don't get your point. The module as it is in the repo "type before description in .info.yml" is being recognized and could be activated, both with Drush and from the Extend page (just tested it, since talk is cheap). Cheers and thanks for mentioning the reversed order in the repo.

[@NowHereUs]

This is what frameworks does to you. We have just learnt how to create more overhead on our site. Leave the fanciness for the site builders. When you are developer just include the file from a module or use autoload. This method is simpler, faster and more understandable. It is always desirable that our sites run quicker due to the reduction of overhead.

[@NowHereUs]

Anyway, your way of explaining things is very good. Keep making more videos. I like your video though I hated the approach drupal has taken.

[@oliver_siegel]

The long term benefits of this are clear though, as your project grows, and different parts of the application reference each other... you won't be able to manage all the includes and autoloads anymore. Then you'll have to implement some type of solution to help you manage all of this complexity. And this solution to help you manage this complexity is exactly what Drupal does! There's definitely a few things that seem unnecessarily complicated about Drupal, but again: Stringing everything together on your own, with includes and autoloads will not be much easier, when you have a large application.