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
The very bottom of the readme says: "file patterns do not currently work in the CLI".
That appears to be untrue, however. Enclosing the wildcard path in single quotes causes Bash to use the literal character value of *. In the command below, I'm running from the Terminal on macOS 10.13.3 in the media_queries folder that ships with purify-css as a test:
purify-css media_queries.css '*.html' -o out.css
From what I can tell, this runs correctly and out.css is indeed missing some CSS.
Question:
Is there another reason you don't officially support wildcards in the CLI besides the escaping required for asterisks in Bash? In short, if I rely on this approach, am I going to hit some weird bugs I'm not aware of?
The text was updated successfully, but these errors were encountered:
The very bottom of the readme says: "file patterns do not currently work in the CLI".
That appears to be untrue, however. Enclosing the wildcard path in single quotes causes Bash to use the literal character value of
*
. In the command below, I'm running from the Terminal on macOS 10.13.3 in themedia_queries
folder that ships with purify-css as a test:From what I can tell, this runs correctly and
out.css
is indeed missing some CSS.Question:
Is there another reason you don't officially support wildcards in the CLI besides the escaping required for asterisks in Bash? In short, if I rely on this approach, am I going to hit some weird bugs I'm not aware of?
The text was updated successfully, but these errors were encountered: