fix: use @eslint/config-array
to resolve paths
#69
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #59
Following the discussions in eslint/eslint#18619 I went ahead and made a proof of concept extraction of the small core logic that ESLint uses to iterate over the files of a directory, using a
ConfigArray
as guidance.I published it at
configArrayFindFiles()
and here is a PR that makes use if it.It uses a fake schema to load the configs into
ConfigArray
as there is no published official one that can be used yet (eslint/eslint#18619 (comment))Hopefully
@eslint/config-array
itself will get aconfigArrayFindFiles()
equivalent eventually, but we need to start somewhere.The way that
configArrayFindFiles()
is constructed it could also simplify ESLint'sglobSearch()
as well if it were to be upstreamed to@eslint/config-array
, as it would separate the concerns of matching byConfigArray
files and ignores and matching by the globs sent intoglobSearch()
when someone wants to lint a set of files.