-
Notifications
You must be signed in to change notification settings - Fork 107
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
fix #1459: диагностика использования встроенной функции как процедуры #1461
Conversation
WalkthroughThe changes involve enhancements to the Changes
Poem
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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration 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.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
src/OneScript.Language/SyntaxAnalysis/DefaultBslParser.cs (1)
714-722
: Improved error handling for built-in functions used as procedures.The added code block enhances error detection by checking if a built-in function is being used as a procedure. This change directly addresses the PR objective of diagnosing the use of built-in functions as procedures.
Some suggestions for improvement:
- Consider extracting the error message to a constant or resource file for easier maintenance and potential localization.
- The
else
block could be simplified by removing the unnecessary variable assignment.Consider applying these changes:
if (LanguageDef.IsBuiltInFunction(_lastExtractedLexem.Token)) { - AddError(LocalizedErrors.UseBuiltInFunctionAsProcedure()); + AddError(LocalizedErrors.UseBuiltInFunctionAsProcedure(_lastExtractedLexem.Content)); } else { - var expected = _tokenStack.Peek(); - AddError(LocalizedErrors.TokenExpected(expected)); + AddError(LocalizedErrors.TokenExpected(_tokenStack.Peek())); }This change assumes that
LocalizedErrors.UseBuiltInFunctionAsProcedure()
can accept a parameter for the function name, which would make the error message more specific and helpful.
@coderabbitai в этом репозитории всегда используй русский язык |
Tip For best results, initiate chat on the files or code changes. @EvilBeaver Спасибо за напоминание. Я буду использовать русский язык в этом репозитории. 🧠 Learnings used
|
Summary by CodeRabbit