Skip to content

Conversation

@sg00dwin
Copy link
Member

@sg00dwin sg00dwin commented Jan 30, 2026

Summary

  • Added "Avoid deprecated components" section to CONVENTIONS.md
  • Documents three key deprecation signals: JSDoc @deprecated tags, import paths containing /deprecated, and DEPRECATED_ file name prefix

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Documentation
    • Added guidance on identifying deprecated components and recommended migration paths.
    • Enhanced type safety recommendations for the codebase.

✏️ Tip: You can customize this high-level summary in your review settings.

Added deprecation signals to check (JSDoc tags, /deprecated paths, DEPRECATED_ prefix)
with code examples in the Patterns section.

Assisted by: Claude Code
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 30, 2026
@openshift-ci-robot
Copy link
Contributor

@sg00dwin: This pull request explicitly references no jira issue.

Details

In response to this:

Summary

  • Added "Avoid deprecated components" section to CONVENTIONS.md
  • Documents three key deprecation signals: JSDoc @deprecated tags, import paths containing /deprecated, and DEPRECATED_ file name prefix

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from jhadvig and rhamilto January 30, 2026 19:27
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2026

@sg00dwin: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@coderabbitai
Copy link

coderabbitai bot commented Jan 30, 2026

📝 Walkthrough

Walkthrough

Documentation updates to CONVENTIONS.md establishing deprecation guidelines for the Frontend Code Conventions. The new section defines three deprecation signals (JSDoc @deprecated tags, /deprecated import paths, and DEPRECATED_ file name prefixes) with examples demonstrating correct vs incorrect usage patterns. Additional guidance addresses AI agent handling of the any type, recommending proper type specifications and null/undefined handling (e.g., string | undefined). The changes consist of 15 new lines with no impact to exported or public entity declarations.

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: adding guidance documentation for avoiding deprecated components to CONVENTIONS.md.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@CONVENTIONS.md`:
- Line 94: Replace the bolded section title "**Avoid deprecated components**"
with a level-4 markdown heading (e.g., "#### Avoid deprecated components") so it
matches the document's heading style (see the "TypeScript Type Safety" heading
used earlier); ensure there's a blank line before and after the new heading for
proper rendering.
🧹 Nitpick comments (1)
CONVENTIONS.md (1)

109-112: Reconsider placement of AI agent guidance.

The guidance about flagging the any type (lines 109-112) is unrelated to deprecated components. It would be more logically organized if:

  1. Moved to the end of the existing "TypeScript Type Safety" section (after line 69), or
  2. Placed in a dedicated "AI Agent Guidelines" section

This would improve document navigation and topical coherence.

📚 Suggested reorganization

Option 1: Move after the existing TypeScript Type Safety section:

 // BAD - Using 'any'
 const data: any = fetchData();

+AI agents should flag use of any type
+- Suggest proper type definitions
+- Check that null/undefined are handled: string | undefined
+- Verify exported types for reusable components


Then remove lines 109-112 from under the deprecated components section.

</details>

</blockquote></details>

</blockquote></details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

);
```

**Avoid deprecated components**
Copy link

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Use proper heading syntax for consistency.

The section title uses bold emphasis (**...**) instead of a heading. For consistency with the document structure (see "TypeScript Type Safety" at line 58), use a level-4 heading.

📝 Proposed fix for markdown heading
-**Avoid deprecated components**
+#### Avoid deprecated components
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
**Avoid deprecated components**
#### Avoid deprecated components
🧰 Tools
🪛 markdownlint-cli2 (0.20.0)

[warning] 94-94: Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

🤖 Prompt for AI Agents
In `@CONVENTIONS.md` at line 94, Replace the bolded section title "**Avoid
deprecated components**" with a level-4 markdown heading (e.g., "#### Avoid
deprecated components") so it matches the document's heading style (see the
"TypeScript Type Safety" heading used earlier); ensure there's a blank line
before and after the new heading for proper rendering.

Copy link
Member

@rhamilto rhamilto left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 30, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 30, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhamilto, sg00dwin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants