Skip to content

AI based docstring enhancements#116

Open
majst01 wants to merge 2 commits intomainfrom
enhance-documentation
Open

AI based docstring enhancements#116
majst01 wants to merge 2 commits intomainfrom
enhance-documentation

Conversation

@majst01
Copy link
Copy Markdown
Contributor

@majst01 majst01 commented Mar 25, 2026

Description

Enhance documentation to be better english and correct punctuation.

Also added validation to partition.management_server_addresses (with my brain)

Used AI-Tools ✨

  • qwen-coder from our dgx-spark

@majst01 majst01 requested a review from a team as a code owner March 25, 2026 15:10
@majst01 majst01 self-assigned this Mar 25, 2026
@majst01 majst01 requested a review from iljarotar March 25, 2026 15:10
Comment on lines -11 to 12
// Get an audit trace
// Returns the audit trace with the specified UUID.
rpc Get(AuditServiceGetRequest) returns (AuditServiceGetResponse) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Reads good, but do we want the Get rpc name to be the first word in doc strings as before?
Regarding Go doc strings. In that case something like Get returns an audit trace

import "metalstack/api/v2/predefined_rules.proto";

// SizeService serves size related functions
// SizeService provides size management operations.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Just picking this as an example. It seems like the AI:

  • added trailing . for service and rpc declarations
  • removed tailing . for fields

Is this intentional and the new convention?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This is part of the bufbuild best practices, we should somewhere document this, but dunno where developers can easily spot this type of documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2 participants