Skip to content

[6.0] Add test case that we don't reload the package if a .swift file get added in a folder that doesn't affect compilation #1512

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

ahoppen
Copy link
Member

@ahoppen ahoppen commented Jun 25, 2024

… added in a folder that doesn't affect compilation

rdar://128573306
@ahoppen ahoppen changed the title Add test case that we don't reload the package if a .swift file get… [6.0] Add test case that we don't reload the package if a .swift file get added in a folder that doesn't affect compilation Jun 25, 2024
@ahoppen
Copy link
Member Author

ahoppen commented Jun 26, 2024

@ahoppen
Copy link
Member Author

ahoppen commented Jun 26, 2024

ahoppen added a commit to swiftlang/swift-package-manager that referenced this pull request Jun 26, 2024
… from `LLBuildManifestBuilder` (#7709)

- **Explanation**: Instead of inspecting file extensions to decide
whether a file might affect build settings, check which files are in
directories that are affecting compilation. This is the same logic that
`LLBuildManifestBuilder` uses and should be more stable. In particular,
this stops us from reloading the package manifest in SourceKit-LSP when
a header file is written to a `.build` directory.
- **Scope**: Only affects SourceKit-LSP
- **Risk**: Low, only affects SourceKit-LSP
- **Testing**: Adding a SourceKit-LSP test case in
swiftlang/sourcekit-lsp#1512
- **Issue**: rdar://128573306
- **Reviewer**: @MaxDesiatov @xedin on
#7699
@ahoppen ahoppen merged commit 252d5be into swiftlang:release/6.0 Jun 26, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant