Is the combinator pattern harmfull for elm-embed?

[emmabastas]

Currently you can combine Embed.Task's with Embed.andThen, i.e one embedder can depend on the result of another one. You could for example use the value of an environment variable as the location for a configuration file read by an embedder, which then further affects the behavior of said embedder as it reads more files from disk. Now you have something that looks like a homecocked build system, which lies far outside the scope of elm-embed.

Are there situations where you genuinely need the power to combine embedders? The most legitimate example I can think of would be to have an environment variable to configure the location of a file to be read on disk. A workaround for that could be to use a symlink instead.