-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: semantic highlight #12
Conversation
Ref: arduino/vscode-arduino-tools#43 Signed-off-by: Akos Kitta <a.kitta@arduino.cc>
Unable to locate .performanceTestingBot config file |
Seems you are using me but didn't get OPENAI_API_KEY seted in Variables/Secrets for this repo. you could follow readme for more information |
Processing PR updates... |
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.
@2lambda123
Thank you for your contribution to this repository! We appreciate your effort in opening pull request.
Happy coding!
Thanks @2lambda123 for opening this PR! For COLLABORATOR only :
|
Check out the playback for this Pull Request here. |
Their most recently public accepted PR is: #11 |
Your organization has reached the subscribed usage limit. You can upgrade your account by purchasing a subscription at Stripe payment link Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect. Current plan usage: 156.20% Have feedback or need help? |
PR Details of @2lambda123 in arduino-arduino-ide :
|
Warning Rate Limit Exceeded@2lambda123 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 11 minutes and 46 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
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.
@2lambda123
Thank you for your contribution to this repository! We appreciate your effort in closing pull request.
Happy coding!
override onStart(): void { | ||
monaco.languages.registerDocumentRangeFormattingEditProvider( | ||
InoSelector, | ||
this | ||
); | ||
monaco.languages.registerDocumentFormattingEditProvider(InoSelector, this); |
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.
The onStart
method registers the current instance (this
) as both a document range formatting edit provider and a document formatting edit provider without ensuring that the instance implements the necessary methods (provideDocumentRangeFormattingEdits
and provideDocumentFormattingEdits
) defined by the interfaces. This could lead to runtime errors if the methods are not implemented or are incorrectly implemented. To improve maintainability and avoid potential runtime issues, it's recommended to explicitly implement these interfaces, ensuring that all required methods are properly defined.
async provideDocumentRangeFormattingEdits( | ||
model: monaco.editor.ITextModel, | ||
range: monaco.Range, |
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.
The method provideDocumentRangeFormattingEdits
is declared but its implementation is not shown. Given the context, it's crucial to ensure that this method handles errors gracefully. If the formatting operation fails (e.g., due to an invalid range or issues within the formatter
), the method should catch any thrown errors and handle them appropriately (e.g., by logging the error and returning a meaningful response to the caller). This is important for maintaining the stability of the IDE extension and providing a robust user experience.
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.
Hey @2lambda123 - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Docstrings: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.
Ref: arduino/vscode-arduino-tools#43
Motivation
Change description
Other information
Reviewer checklist