So I have a lot of resources divided in directories that I have placed under my_pod/res.

My build.fan file references

resDirs = [`res/`]

I have noticed that only the files in res/ get build into the pod, and that the subdirectories are not included.

I know I can programmatically build resDirs to include all the directories, but I was curious to know about this behaviour, why do subdirectories under res/ get ignored?

Thanks!

All the build script configuration fields take lists of URIs, but do not automatically recurse. Not any specific reason really - just the way it got coded up. Although I do like the ability see all the dirs in my build script and ability to comment out a specific directory (even if its a bit more verbose).

Works the same way for srcDirs - and I think that consistency is correct. And that model is certainly valuable for commenting out source easily. So while inconvenient for resources, I still think this design makes the most sense. But I'm open to change if others feel differently.

Maybe an optional syntax to explicitly specify recursion?

resDirs = [`res/**`]

or something?

Yeah, but then we enter the domain of include and exclude filters, regex, etc.

Things are simple as they are, and this is not that big deal, I was just asking out of curiosity :-)

If there's enough demand, maybe a set of helper functions on the parent BuildPod, could fill up resDirs (and others) according to a concrete pod-level defined criteria.

Also remember that build files are executable scripts, so you can just run a glob in your constructor to compute the value of the resDirs field. That is the really cool thing about Fantom build files - they aren't just "dumb XML" files :-)