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

Error object is missing the missing property in 5.0.0 #251

Open
soluml opened this issue Sep 27, 2020 · 3 comments
Open

Error object is missing the missing property in 5.0.0 #251

soluml opened this issue Sep 27, 2020 · 3 comments

Comments

@soluml
Copy link

soluml commented Sep 27, 2020

I have a custom resolver that depends on the missing property of an error object returned in the callback after attempting to resolve a path. This was done so that I can attempt to do some further path correction (like globbing). In the latest version (5.0.0), the missing field has been removed from the error object.

Is this something that we could get back? Either in the error object or as some additional property so that we can see what paths were attempted for resolution?

@alexander-akait
Copy link
Member

alexander-akait commented Sep 28, 2020

No, it is breaking change, you should not rely on missing

@sokra
Copy link
Member

sokra commented Sep 28, 2020

You can get this info by passing a missingDependencies property to the resolveContext. It should be an object with an add method, e. g. a Set. During resolving all missing items will be added. There is also fileDependencies for files and the existence of directories and contextDependencies for the content of directories.

@alexander-akait
Copy link
Member

Answer above, my mistake, sorry, need to document

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

No branches or pull requests

3 participants