Skip to content

Conversation

@norascheuch
Copy link
Contributor

Instead of removing the information completely we will show primary and secondary rate limit information in the extension output.

Checklist

  • CHANGELOG.md has been updated to incorporate all user visible changes made by this pull request.
  • Issues have been created for any UI or other user-facing changes made by this pull request.
  • [Maintainers only] If this pull request makes user-facing changes that require documentation changes, open a corresponding docs pull request in the github/codeql repo and add the ready-for-doc-review label there.

@norascheuch norascheuch requested a review from a team as a code owner September 14, 2023 08:37
}>,
token: CancellationToken,
credentials: Credentials,
logger: NotificationLogger,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To make this easier to test, I think we should keep using the logger (although it can be the BaseLogger instead of the NotificationLogger) instead of importing extLogger directly. I think we're moving away from importing extLogger directly and always trying to use a Logger interface.

@norascheuch norascheuch force-pushed the nora/remove-rate-limit-code-search branch from 64a0a60 to 7af8b7a Compare September 28, 2023 08:50
@norascheuch norascheuch merged commit 859eca0 into main Sep 28, 2023
@norascheuch norascheuch deleted the nora/remove-rate-limit-code-search branch September 28, 2023 09:57
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.

3 participants