feat: add RHDA_TOKEN param to Exhort JS API request #213
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
IlonaShishov
force-pushed
the
feat/rhda-key
branch
from
d58ba65 to
2f90d2e
Compare
IlonaShishov
changed the title
IlonaShishov
force-pushed
the
feat/rhda-key
branch
from
2f90d2e to
0de8156
Compare
zvigrinberg
approved these changes
Oct 2, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Passed the TELEMETRY_ID environment variable from VSCode extension (where is it generated) to LSP Server.
Included TELEMETRY_ID as RHDA_TOKEN environment variable in options passed to Exhort JS API component analysis request.