Make `ignore` platform/os agnostic? about node-ignore HOT 4 CLOSED

Crap 😧!!

That changes everything. I didn't know about this till now. I have published a bunch of stuff in past that blindly separates paths on [\\\/] and moves on with the day. I'll have to fix all those things.

I kept hating win32 for being the only one bad kid for not following the convention of using forward slashes like others but at least it isn't ambiguous in the type of slashes it uses in path(s).

Well, I guess I'll retract this request unless you have anything in mind.

from node-ignore.

And just to add on why this would be awesome, we should think of ignore as a "path" matching library instead of a "string" matcher.

The "semantic" correctness instead of "syntactic".

ignore should be the answer to the question:
Does this pattern match the following resource?

And ignore saying no to the above question when given dist/** and dist\scripts\index.js respectively doesn't sound very right.

from node-ignore.

I thought just converting the path dist\scripts\index.js to dist/scripts/index.js is dangerous, because some linux os supports directory names or file names that contain back slashs (\). For example, foo\bar/baz.js is a valid file path on Mac OS, in which a javascript file bar.js is inside the one-depth directory foo\bar.

If you have a webapp that helps people to test the .gitignore rules and it supports windows paths, maybe it is better to convert the paths before using node-ignore.

from node-ignore.

Close for now

from node-ignore.