microsoft / microsoft/vscode-java-dependency
Adding a source folder directly, rather than its contents
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 199
- Forks
- 105
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 27
Description
Typically, you'll have a source structure like so: "src/package/path/MyClass.java". When you add src to the list of sources, it will include the contents, e.g. package.path.MyClass. That is sensible.
There is a project I'm working on that has a resource folder which I'd like to add directly. E.g. Add the folder itself, not the folder's contents. For example, suppose I have structure: "images/img.png". Currently, if I add images to sources, then img.png gets copied directly to the build directory, instead of images/img.png. As a workaround, I have to rearrange the structure to be something like "src_images/images/img.png", or move into "src/images/img.png". Hope that makes sense.
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
The issue does not name implementation files or tests. Start by locating the extension's handling of configured source folders and reproduce the images/img.png example; done means adding images preserves that folder in the build output while existing source-package behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, typescript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100