No way to ignore a specific file within a specifically added directory in .claspignore

[nyoma-diamond]

Expected Behavior

If .claspignore contains
**/**
!**/gs/**
gs/genericFile.js

clasp should ignore everything that isn't in /gs and ignore genericFile.js

Actual Behavior

Clasp still pushes genericFile.js; pushes contents of /gs

[nmccready]

Seeing the same behavior.

[amerrnath-murugan-E0711]

Any updates on this bug, i am still seeing the bug in version 1.5.3

[kferrone]

I definitely can't ignore the node_modules folder either???

[takanakahiko]

I propose to use multimatch.
This can get results like gitignore.

var anymatch = require('anymatch');
var micromatch = require('micromatch');
var multimatch = require('multimatch');

anymatch(['**/**', '!**/gs/**', 'gs/genericFile.js'], 'hoge.js')
// true
anymatch(['**/**', '!**/gs/**', 'gs/genericFile.js'], 'gs/genericFile.js')
// false
anymatch(['**/**', '!**/gs/**', 'gs/genericFile.js'], 'gs/hoge.js')
// false

micromatch(['hoge.js','gs/genericFile.js','gs/hoge.js'], ['**/**', '!**/gs/**', 'gs/genericFile.js'])
// [ 'hoge.js' ] <- bad

multimatch(['hoge.js','gs/genericFile.js','gs/hoge.js'], ['**/**', '!**/gs/**', 'gs/genericFile.js'])
// [ 'hoge.js', 'gs/genericFile.js' ]

---

EDIT :

anymatch & micromatch : Priority of Negation patterns > Priority of not Negation patterns
multimatch : Priority of Previous patterns < Priority of following patterns

[grant]

@takanakahiko Sounds good! PRs welcome.

[fahadnaeem]

I want to ignore gulpfile.js using .claspignore but I'm unable to do. I'm using clasp@3

[grant]

clasp@3 isn't out, but I assume there are still issues with this?

[PopGoesTheWza]

PR #620 should fix this

[PopGoesTheWza]

@napostrophe can you try with clasp 2.2.0 if the issue still occurs?

[armand1m]

the error still happens in clasp 2.3.0

[PopGoesTheWza]

@armand1m Could you please provide some context about your issue?

Do you have a sample .claspignore to reproduce the issue?

[ghost]

[PopGoesTheWza]

@grimmigenaai not sure if your issue is related to Microsoft Windows. What is the output of clasp status

[ghost]

@PopGoesTheWza

so, here is the answer: clasp picks up the .gitignore :)
.claspignore

.gitignore

[PopGoesTheWza]

@grimmigenaai Fact is... .claspignore is correctly detected and parsed. But the file matching that follow is broken.

I can trace down the change which introduced the problem to about a year ago (and I am to blame for that change)

I'll try to fix it in the coming week as I refactor this part of the code.

[ghost]

w00t :D/

[PopGoesTheWza]

@grimmigenaai (and others) can you test with the #791 unofficial release?

npm uninstall -g @google/clasp && npm install -g forked-clasp
clasp --version
# should be 2.4.0 or more

[jackhartnett]

@PopGoesTheWza

I am still experiencing this issue on version 2.4.0.

I'm using a sample .claspignore file from the documentation. This has been an extremely frustrating morning to say the least.

Edit (again): I reverted back from 2.4.0 to 2.3.0 and I have gotten "clasp push" working again. Every one of my files was being flagged as ignored despite the contents of .claspignore

[PopGoesTheWza]

@jackhartnett Please clarify the status on this issue

[Yash-Singh1]

Issue still persists on clasp 2.4.1.

[koconnor3]

I am also still seeing this issue on 2.4.1 (cannot .claspignore node_modules, which is extremely annoying)

[chardskarth]

Should this be closed? I'm not able to replicate in 2.4.2