HYPERFLEET-1090 - refactor: rename WIFConfig to WifConfig (PascalCase)#5
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Central YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (9)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThis PR standardizes the WifConfig resource naming convention across the API spec. The version is bumped from 1.0.21 to 1.0.22. All occurrences of Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 6✅ Passed checks (6 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Adopt PascalCase for the WifConfig resource kind to stay consistent with other HyperFleet resource naming (e.g., NodePool). - Rename all TypeSpec models, consts, and aliases from WIFConfig to WifConfig - Update service interface, operation IDs, and tags to use WifConfig casing - Regenerate openapi.yaml and swagger.yaml with new schema names - Bump version to 1.0.21 and add CHANGELOG entry
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ciaranRoche The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@coderabbitai review |
✅ Action performedReview finished.
|
7ce8014
into
openshift-hyperfleet:main
Adopt PascalCase for the WifConfig resource kind to stay consistent with other HyperFleet resource naming (e.g., NodePool). (see hyperfleet-api #198)
Summary
Test Plan
make test-allpassesmake lintpassesmake test-helm(if applicable)