[RFC]: add `@stdlib/fs/resolve-parent-paths-by`
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 1.3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 611
Description
### Description
This RFC proposes adding `@stdlib/fs/resolve-parent-paths-by` similar to [`@stdlib/fs/resolve-parent-path-by`](https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/fs/resolve-parent-path-by), which instead of a single path, accepts an array of paths and resolves according to the `predicate`.
Similar to [`@stdlib/fs/resolve-parent-paths`](https://github.com/stdlib-js/stdlib/tree/develop/lib/node_modules/%40stdlib/fs/resolve-parent-paths) we would want to support multiple modes of operation.
### Related Issues
Related issues #2565
### Questions
No.
### Other
No.
### Checklist
- [X] I have read and understood the [Code of Conduct](https://github.com/stdlib-js/stdlib/blob/develop/CODE_OF_CONDUCT.md).
- [X] Searched for existing issues and pull requests.
- [X] The issue name begins with `RFC:`.
Contributor guide
Research direction
Start by reading @stdlib/fs/resolve-parent-path-by and @stdlib/fs/resolve-parent-paths, then compare the related issue #2565 for the intended scope. Define the array-of-paths behavior, predicate handling, and supported modes before checking the analogous implementations and their tests; done means the new module matches the established APIs and mode semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100