Skip to content

Conversation

@roothorp
Copy link
Collaborator

@roothorp roothorp commented Dec 4, 2025

Summary

Fixes some missing or incomplete CRD comments, mainly surrounding status. This seems to give us ~100% comment coverage on CRD fields, so the docs should be complete after this.

Proof of Work

Checklist

  • Have you linked a jira ticket and/or is the ticket in the title?
  • Have you checked whether your jira ticket required DOCSP changes?
  • Have you checked for release_note changes?
  • Have you signed our CLA?

Reminder (Please remove this when merging)

  • Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
  • Remember the following Communication Standards - use comment prefixes for clarity:
    • blocking: Must be addressed before approval.
    • follow-up: Can be addressed in a later PR or ticket.
    • q: Clarifying question.
    • nit: Non-blocking suggestions.
    • note: Side-note, non-actionable. Example: Praise
    • --> no prefix is considered a question

@roothorp roothorp requested a review from a team as a code owner December 4, 2025 11:39
Comment on lines 40 to 41
// Flag that indicates whether someone hashed the custom shard key. If this parameter returns false, this cluster uses ranged sharding.
IsShardKeyUnique *bool `json:"isShardKeyUnique,omitempty"` // Flag that specifies whether the underlying index enforces a unique constraint.
Copy link
Collaborator

Choose a reason for hiding this comment

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

q: Does this use the comment at the top or on the side?
I would probably leave just one of them.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It seems to ignore the inline/side comments, and just uses the ones above. I've removed the inline ones here, because it was just duplicating the information, but it's good to know that we can still use inline for dev-targeted comments.

@roothorp roothorp force-pushed the cloudp-355972-more-crd-comments branch from a39c339 to 81a9885 Compare December 4, 2025 15:05
@roothorp roothorp merged commit 2c8cbcf into main Dec 4, 2025
16 checks passed
@roothorp roothorp deleted the cloudp-355972-more-crd-comments branch December 4, 2025 15:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants