Load subfolders

🚀 Feature Proposal

Given the tree:

• folder
  • file a
  • folder lv 1
    • file b
    • folder lv 2
      • file c

Only the file a is loaded and the other directories are ignored

In this example, I would register every folder and put all the files in the same context.

Motivation

This lets the user organize the application in a more flexible structure where the URLs (except some prefix-override) is mapped to the project tree

Example

fastify.register(require('fastify-autoload'), {
  dir: x,
  recursive: true // as rm -rf 😅
})

[SkeLLLa]

I’ve implemented something similar: https://github.com/SkeLLLa/fastify-autoload-recursive some time ago. Feel free to reuse the code if you’d like.

And here some notes that I’ve found during implementing it:

Sometimes it’s useful to define file order in which they are registered. For example if we have plugin that adds shared shema and plugin that adds route in the same folder, then schema should be registered before. So that’s why I created 3 patterns for files: schema, options, ignore. Options file contains a function that may return additional options (that could be calculated dynamically, so you couldn’t pass them directly) and after that they are merged with static options and passed to register function. Such files evaluated in first place. Schema files contain shared schemas that are used later. Such files are registered before other files, so later we can use shared shemas. Ignore patter is used to ignore files, for example, some helpers with common code that are used only in specific plugin or service. Those are ignored by autoloader and required directly in other files.

I don’t know if schema and options settings are useful for others, but I think that ignore pattern (for files and folders as well) here is a must have feature for recursive loading.

[alemagio]

If you don’t mind I’ll try to do it. Good part of being at home 😅 having time for open source