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
When there's a need to have multiple Dockerfiles in a single directory, it's relatively common to name them Dockerfile.*, e.g. Dockerfile.dev, Dockerfile.prod.
I've tried configuring dprint to match such files, but it doesn't seem to work:
If I have Dockerfile and Dockerfile.prod at the root of my project, running dprint output-file-paths finds Dockerfile but not Dockerfile.prod. It doesn't even work if I explicitly add **/Dockerfile.prod to includes.
If I add **/*.Dockerfile to includes and mv Dockerfile.prod prod.Dockerfile, it does find the file, but this isn't our preferred naming convention.
dprint-plugin-dockerfile version: 0.3.0
The text was updated successfully, but these errors were encountered:
When there's a need to have multiple Dockerfiles in a single directory, it's relatively common to name them
Dockerfile.*
, e.g.Dockerfile.dev
,Dockerfile.prod
.I've tried configuring dprint to match such files, but it doesn't seem to work:
If I have
Dockerfile
andDockerfile.prod
at the root of my project, runningdprint output-file-paths
findsDockerfile
but notDockerfile.prod
. It doesn't even work if I explicitly add**/Dockerfile.prod
toincludes
.If I add
**/*.Dockerfile
toincludes
andmv Dockerfile.prod prod.Dockerfile
, it does find the file, but this isn't our preferred naming convention.dprint-plugin-dockerfile version:
0.3.0
The text was updated successfully, but these errors were encountered: