Source directory shouldn't override fully specified paths
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 17k
- Forks
- 3.4k
- Avg merge
- 7h 42m
- Merged PRs (30d)
- 26
Description
When using the following command line:
lessc --include-path=src/app/less:bower_components/bootstrap/less bower_components/bootstrap/less/bootstrap.less
The contents of src/app/less are overridden by bower_components/bootstrap/less in the search path for imports. If, instead, the input comes from stdin, i.e.:
cat bower_components/bootstrap/less/bootstrap.less | lessc --include-path=src/app/less:bower_components/bootstrap/less -
In this second case, the imports follow the order specified in the command line. It seems intuitive that a specified order including the directory for the source file should be left unmodified.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CLI handling of --include-path and reproduce both lessc commands from the issue. Trace how the source directory is added to the import search path; done means an explicitly ordered --include-path remains unchanged for a file input, matching the stdin behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100