Consecutive separator behaviour
erikgeiser opened this issue · 0 comments
erikgeiser commented
As was already discussed in #20, patterns containing **/*
may lead to unexpected results for most users. After porting https://github.com/goreleaser/nfpm to glob
, this was reported as a regression (goreleaser/nfpm#256).
Currently, the pattern test/**/*
does not match test/file
but it does match test//file
(https://play.golang.org/p/geU9afuijny). While this is technically correct, it is not what users expect, since test/file
and test//file
are identical in the context of file systems.
This situation could be solved by modifying the AST. This could also be added as an option using the pattern described in #45.