swiftlang / swiftlang/swift-java
Make sure we don't cause stray o and swiftdeps files in root directories
Open
Nobody has claimed this yet.
feature:wrap-java
- Dominant language
- Swift
- Stars
- 1.2k
- Forks
- 123
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 16
Description
Some folks reported we generated them into source root directories and I've seen it on occasion as well.
Make sure we don't do and don't pollute our user's workspace
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 by reproducing the generation in a workspace with source-root directories and trace which build or generation entry point places the .o and .swiftdeps files there. Done means the workflow no longer leaves those files in users' source roots; the issue names no specific file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100