Dynamic definition of content of @Sources via Sources supplier method/class? (SourcesLocator)

[thungsten]

I need to have a list of places scanned for properties files. The number of file paths paths and exact definition of file paths may change. That's why it is not possible to use the current @Sources annotation without adding limitations.
In JUnit e.g. it is possible to define a dynamic stream/list of parameter values for @ParametrizedTest.

And in the Owner issues I saw a old suggestion/idea:

Eventually, if the end user needs a more complex strategy to identify from where to load
the properties files, maybe we can let him to specify a @SourcesLocatorClass(MySourceLocator)
and have the end user implement the algorithm
to identify a single URI or a list of URI to load the properties.

At the moment, new features added are lacking documentation (and this means that they
are incomplete for a release), and unfortunately I don't have much time to dedicate to
this project.

Originally posted by @lviggiano in #173 (comment)

Has that been implemented?

Best regards