--input=SingleFile.njk --output=. processes nothing

[zachleat]

As you can see in the screenshot, !./** takes precedence over ./filename.njk

[rendall]

Perhaps --output=. always triggers this bug.

This bug is also triggered in the case where the input directory is a subdirectory of the output directory. e.g. eleventy --input=src --output=. (and no combination of directory path seems to work around it:
--output=src/.., etc)

cd src and then eleventy --input=. --output=../ is a workaround.

(for version 0.5.4)

[rendall]

This configuration in .eleventy.js will result in the output directory path ./false:

dir: {
  input: "src",
  output: ""
 }

I'm mentioning it here because I suspect it's related, because this configuration

dir: {
  input: "src",
  output: "."
 }

results in no files processed.

[rendall]

Perhaps related to #232

dir: {
  input: "src",
  output: "/"
 }

results in the output directory being the root directory! That's unexpected.

[kleinfreund]

I expect the output directory configured with output: "/" to be the root directory. Same applies for input: "/".

That said, I believe Eleventy shouldn’t allow neither the input nor the output directory to be outside of the project directory.

[zachleat]

@kleinfreund hmm good point that does seem potentially dangerous.

[kleinfreund]

I don’t think this is an issue. The input file location should rule out the output directory to be the same because people will eventually end up overwriting their own files. In general, the output directory should never be the Eleventy project directory.

[zachleat]

Fixed with #1129 but tests just added in 8c3377c