-
Notifications
You must be signed in to change notification settings - Fork 53
enhance os library annotations #919
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
base: main
Are you sure you want to change the base?
Conversation
Summary of ChangesHello @tinyleolin, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request enhances the type annotations within the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request enhances the EmmyLua annotations for the os library by introducing a std.osdateparam class for os.time and making std.osdate inherit from it. The overloads for os.date are also updated to use the more specific std.osdate type. These are good improvements for type safety and clarity. I've left one comment with suggestions to further improve the correctness and maintainability of the std.osdate class definition.
| ---@field yday (integer|string)? 1-366 | ||
| ---@field isdst boolean? daylight saving flag, a boolean. | ||
|
|
||
| ---@class std.osdate : std.osdateparam |
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.
While making std.osdate inherit from std.osdateparam is a good step, there are a couple of follow-up improvements for std.osdate to make the annotations fully correct and maintainable:
- Redundant fields: The fields
year,month, andday(lines 37-39) are now inherited fromstd.osdateparamand are identical. They can be removed fromstd.osdateto avoid duplication. - Incorrect
isdsttype: Theos.datedocumentation (line 67) states that theisdstfield may be absent. However, in thestd.osdateclass definition (line 45),isdstis defined as mandatory (boolean). It should be marked as optional (boolean?) to correctly reflect the behavior ofos.date.
No description provided.