Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid rule overrides #1

Closed
wants to merge 3 commits into from
Closed

Avoid rule overrides #1

wants to merge 3 commits into from

Conversation

CoffeeChaton
Copy link

sugget 1

Sugget to providing more documentation to user code filter rules .

I am search for "why fs.CpSync() is not a function", until i Hover to fs.CpSync(), it need node.js v16.7.0.

sugget 2

When I wrote My_filter() , the static files also copy, because of filter: options.filter || filter , My_filter() directly covered your rules .

# sugget 1
Sugget to providing more documentation to user code `filter` rules .

I am search for "why `fs.CpSync()` is not a function", until i Hover to `fs.CpSync()`, it ***need node.js v16.7.0***.

# sugget 2

When I wrote `My_filter()` , the **static files also copy**, because of `filter: options.filter || filter` , `My_filter()` directly covered your rules .
@nickjj
Copy link
Owner

nickjj commented Jan 30, 2022

Hi,

I could see adding docs about the Node 16.x dependency. Node 16.x is the latest LTS btw, 14.x is considered to be in maintenance mode.

I'm not sure I'm following your other change tho. Your custom filter function should completely override the built in filter function that comes from this extension. That would be the indented behavior and in most cases you wouldn't have to do this because the built in filter function is what does the md5 comparison for you before copying. Did you have something else in mind?

@CoffeeChaton
Copy link
Author

Thank you very much for your answer, then I have no problem. Thank you

@nickjj
Copy link
Owner

nickjj commented Jan 30, 2022

No problem, I just updated the readme file in the installation section to call needing Node 16.7+ too in f3ed596. Thanks for calling that out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants