-
Notifications
You must be signed in to change notification settings - Fork 718
Clone watcher
compiler configurations before comparison to prevent unintended recompilation
#1197
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
Conversation
Tagging @jakebailey because of his involvement in both #778 and #1156 Also tagging @sheetalkamat because of her involvement in #1078, which appears to be tangentially related to this issue: the difference in configuration appears to come from the cache not being included in one of the configuration objects being compared, while it is included in another. |
Co-authored-by: Jake Bailey <[email protected]>
watcher
compiler configurations before comparison to prevent unintended recompilation
Co-authored-by: Jake Bailey <[email protected]>
Hi @DanielRosenwasser thanks for your review. I just updated the PR with an additional comment. Could you approve again? |
…unintended recompilation (microsoft#1197) Co-authored-by: Jake Bailey <[email protected]>
…unintended recompilation (microsoft#1197) Co-authored-by: Jake Bailey <[email protected]>
Similar to the issue reported in #778, #1156 appears to have introduced an issue such that
--watch
mode continuously rebuilds a project due to configuration changes, even if no config changes have occurred.This PR aims to address that issue by only comparing the relevant parts of the configuration, while ignoring differences in other parts.
With this change:
Before this change (current
main
branch):