You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
start test with docker run -v $(pwd):/test --rm wjdp/htmltest
Then the config is ignored and all folders e.g node_modules is scanned.
.htmltest.yml
DirectoryPath: public
Source files
Please include any relevant lines from the directory you were using htmltest on. Ideally you would be able to find a single line that if included causes this bug.
Expected behaviour
I expect the config is read, even when a path is specified via argument
Actual behaviour
config is ignored, caused by the path specification in the Dockerfile
Versions
OS: [alpine 3.9 (from dockerfile)]
htmltest: [e.g. 0.10.1, run htmltest -v] 0.15.9
Additional context
One mitigation would be to remove that mentioned line from the dockerfile, but maybe this would also help for "normal" usage, that the app looks for a configfile in the current working directory.
The text was updated successfully, but these errors were encountered:
Describe the bug
When running the default command from the readme, the configfile is ignored
To Reproduce
Example layout
. ├── .htmltest.yml ├── README.md ├── node_modules │ ├── .bin │ ├── .yarn-integrity │ ├── @babel │ ├── accepts ├── public │ ├── index.html │ └── style.css
docker run -v $(pwd):/test --rm wjdp/htmltest
Then the config is ignored and all folders e.g
node_modules
is scanned..htmltest.yml
Source files
Please include any relevant lines from the directory you were using htmltest on. Ideally you would be able to find a single line that if included causes this bug.
Expected behaviour
I expect the config is read, even when a path is specified via argument
Actual behaviour
config is ignored, caused by the path specification in the Dockerfile
Versions
htmltest -v
] 0.15.9Additional context
One mitigation would be to remove that mentioned line from the dockerfile, but maybe this would also help for "normal" usage, that the app looks for a configfile in the current working directory.
The text was updated successfully, but these errors were encountered: