-
Notifications
You must be signed in to change notification settings - Fork 33
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
Rejecting / Excluding Files | broccoli-funnel #172
Comments
And this is specifically to reject/exclude input files right? If so @SparshithNR's https://github.com/SparshithNR/fs-merger may fit the bill for broccoli-persistent-filter to use, instead of direct this.inputPaths access. |
I am trying to integrate the https://github.com/SparshithNR/fs-merger, so that class FileModifier extends BroccoliPlugin {
constructor(nodes, options = {}) {
super(nodes, {
name: options.name,
annotation: options.annotation,
persistentOutput: true
});
} Here |
@stefanpenner It seems to me that what is being requested is an option that causes only files processed by the filter to pass through to the output tree. @buschtoens is that sufficient? |
@chriseppstein @stefanpenner - I've come across this issue as I am just starting to use I guess I could funnel beforehand but I do want some of the other files to be in the tree/ watched as I need to read from them in |
@vitch Yeah, I think you'd have to funnel after filtering in that case, it's a little extra work, but not a ton (the files are just symlinked). |
Now that we have Dependency Tracking #168, this plugin becomes much more interesting for bundler-liker build scenarios, where
n
files get merged into 1 or fewer thann
files.It would be nice, if
broccoli-persistent-filter
could add a hook to reject a file from the build (similar togetDestFilePath
), removing the need for a subsequentbroccoli-funnel
.The text was updated successfully, but these errors were encountered: