-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Always send configFileDiagEvent and instead set triggerFile for more consistency #58462
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
const project = this.createAndLoadConfiguredProject(configFileName, reason); | ||
project.skipConfigDiagEvent = true; | ||
project.updateGraph(); | ||
private createLoadAndUpdateConfiguredProject(configFileName: NormalizedPath, reason: string, triggerFile: NormalizedPath | undefined) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed all the createConfiguredProjectAnd** methods except this one as now createConfiguredProject
takes reason and sets the pending level to Full to correctly represent the state.
} | ||
] | ||
} | ||
} | ||
Info seq [hh:mm:ss:mss] event: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is example of duplicate configFileDiagEvent
Is there a linked bug that this fixes? |
We have following rules on when to send the
configFileDiagEvent
configFileDiagEvent
configFileDiagEvent
event for all loaded/looked up projects so that we can figure out if there are errors in config file which is the reason why the file went into inferred projectconfigFileDiagEvent
configFileDiagEvent
if the diagnostics changed any time program update happensSo this handles that ensuring we arent sending duplicate event
468d91c deletes the unnecessary comment about loading/reloading configured project
f738ccd actual change