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
Stack trace (if provided) contains mobi.hsz.idea.gitignore package name
Description
It would be nice to have some way to tell plugin, which directory is considered to be "root" for edited .dockerignore file.
Sometimes, Dockerfiles and corespoinding .dockerignore files are organized in project subdirectories. When editing such file, file/directory entries are being reported as non-existent ("XYZ entry is never used") - plugin looks into location of .dockerignore file, not to directory where actual build is executed - i.e.:
docker build -f docker/backend.Dockerfile .
Some form of annotation provided via comment could be used, to tell plugin. which directory is actual build root - i.e.
# root ../..
node_modules
...
Expected behavior:
Some way to tell plugin to look to different directory.
Actual behavior:
No way (at least none documented)
Versions
Plugin:
4.1.0
The text was updated successfully, but these errors were encountered:
postolka
changed the title
Annotations for .dockerfile root directory
Annotations for .dockerignore root directory
May 12, 2021
Prerequisites
mobi.hsz.idea.gitignore
package nameDescription
It would be nice to have some way to tell plugin, which directory is considered to be "root" for edited
.dockerignore
file.Sometimes, Dockerfiles and corespoinding .dockerignore files are organized in project subdirectories. When editing such file, file/directory entries are being reported as non-existent ("XYZ entry is never used") - plugin looks into location of
.dockerignore
file, not to directory where actual build is executed - i.e.:docker build -f docker/backend.Dockerfile .
Some form of annotation provided via comment could be used, to tell plugin. which directory is actual build root - i.e.
Expected behavior:
Some way to tell plugin to look to different directory.
Actual behavior:
No way (at least none documented)
Versions
Plugin:
The text was updated successfully, but these errors were encountered: