Fix no-field message when All tab is selected#104
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthrough
ChangesNo Field Found Tab Awareness
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related issues
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint install failed. For unrecoverable errors, disable the tool in CodeRabbit configuration. 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 |
Description
Addresses downstream issue KaotoIO/kaoto#3281.
When the form empty state is shown while the selected tab is already
All,NoFieldFoundcurrently still prompts users to switch to the All tab. This keeps the existing switch action forRequired/Modified, but renders a plain no-results message whenAllis already selected.Type of Change
How Has This Been Tested?
corepack yarn test src/form/Form/NoFieldFound.test.tsx --runInBandcorepack yarn test --runInBandcorepack yarn build:libcorepack yarn prettier --check src/form/Form/NoFieldFound.tsx src/form/Form/NoFieldFound.test.tsxcorepack yarn eslint src/form/Form/NoFieldFound.tsx src/form/Form/NoFieldFound.test.tsxChecklist
Summary by CodeRabbit
Bug Fixes
Tests