Hello - I'm curious if you'd be interested in a proposal to support filtering before resolving with file-cabinet. What I'm trying to accomplish is to prevent certain dependencies from being considered at all so that I can fail fast when something can't be resolved. Currently, the filter option filters after dependencies have been extracted and resolved, and there's no way to filter these before they're added to the nonExistent array. If it were possible to filter before resolution, I could prevent these dependencies from being considered at all. I can't easily post-process nonExistent because I need to know from which file the dependencies were from. So, I'm thinking if the filtering functionality were augmented to support filtering pre-resolution, I could just hook into that.
If this sounds interesting, I can work on a PR. I imagine we can't just move the filter function call before the file cabinet call since that would be a breaking change, but could maybe add an additional config or similar? Thanks!
Hello - I'm curious if you'd be interested in a proposal to support filtering before resolving with file-cabinet. What I'm trying to accomplish is to prevent certain dependencies from being considered at all so that I can fail fast when something can't be resolved. Currently, the
filteroption filters after dependencies have been extracted and resolved, and there's no way to filter these before they're added to thenonExistentarray. If it were possible to filter before resolution, I could prevent these dependencies from being considered at all. I can't easily post-processnonExistentbecause I need to know from which file the dependencies were from. So, I'm thinking if the filtering functionality were augmented to support filtering pre-resolution, I could just hook into that.If this sounds interesting, I can work on a PR. I imagine we can't just move the
filterfunction call before the file cabinet call since that would be a breaking change, but could maybe add an additional config or similar? Thanks!