Description
There is a problem with file path verification in the toolchain if you include a file from a file that is also in turn included from a top level asciidoc file. Looks like what’s happening is that the toolchain is checking the path from the file the include is in, but the include itself needs to have a path from the top level file where the file the include is in, is included from.
So if you put in a path with one too many “..“’s in then the toolchain works and builds the site. But then the site renders with a “can’t find included file error inline” and if you put in a path with the correct relative path, the toolchain barfs and wont’ compile the site.
Low priority. Do not work on this, for now the workaround is "don't include a file from an already included file." Simples!