Start integrating the feature into Moodle core

[juho-jaakkola]

I recently made a feature request about a front controller for Moodle: https://tracker.moodle.org/browse/MDL-60140

Now I came across your plugin, and realized you've already started implementing that feature!

I bet you have plenty of insight on the matter, so it would be great if you could provide some kind of list or roadmap of needed changes into the feature request.

It would great if all the future work would go directly into Moodle core as an officially supported feature.

[brendanheywood]

hi @juho-jaakkola I'll add some thoughts to that tracker

[FMCorz]

Hi @juho-jaakkola, check out how I implemented routing in my own plugin. I talk about it in #116. I do agree that such a feature should be in core instead though.

[juho-jaakkola]

Getting slightly off-topic, but I'll write this down somewhere before I forget it:

Besides front controller, I've also been looking into making Moodle installable as a composer dependency. I wonder if the front controller could be implemented (at least as the first step) into the composer project base instead of Moodle core.

Take a look for example at these two examples, where not only the modules/plugins/libraries, but also the version of the framework itself is managed through a single composer.json file at the root of the project:

• https://github.com/drupal-composer/drupal-project
• https://github.com/elgg/starter-project

This approach would allow:

• The front controller to be located at the project base instead of Moodle core (which would get installed to vendor/moodle/moodle/)
• Developing the approach independently from Moodle core
• Adding logic like reading for example a routes.yml file from each plugin's directory before deciding where to route the request (the file would map paths such as /myplugin/123 to routes, which would trigger e.g. page specific controllers)