should support the folder defined in the plugin

Folder or folders (there might be multiple).

Backward-Compatible Solution Proposal: Dynamic Filesystem Root Support for

To enhance flexibility without breaking existing functionality, I propose an update to the field that optionally supports dynamic filesystem roots.

Implementation:

• Extend the directory attribute to accept a value like @filesystem:adapter, e.g. @filesystem:local
• If the prefix @filesystem: is detected, resolve the adapter name and fetch the root_folder or repeatable directories param from the plugin
• Loop through each configured directory (if multiple) and merge their subfolders into the options list
• If no match or plugin is missing, fallback to the existing hardcoded path like images

What Stays the Same:

• If directory="images" or any static folder is provided, existing logic remains unchanged
• No modifications required in existing XMLs, templates, or plugin configs
• Works exactly as before for all current use cases

Benefits:

• Adds support for dynamic folder roots based on active Filesystem plugin
• Completely non-breaking and opt-in
• Useful for future use cases like using S3, external media storage, or dynamic local folders

I'm happy to contribute the updated getOptions() method or submit a patch. Let me know if this can be considered for core inclusion.

@brianteeman review above solution. Happy to contribute!