fix: Move expires_in field after scope in OAuth2 datasource config#41821
fix: Move expires_in field after scope in OAuth2 datasource config#41821YoussefMansour9 wants to merge 2 commits into
Conversation
- Moved Authorization expires in (seconds) field to appear right after Scope(s) field - Added conditional check to only show for Authorization Code grant type - This improves UX by grouping all authentication-related fields together Fixes appsmithorg#31059
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe expires-in field in the OAuth2 datasource form is reorganized to appear in the shared OAuth2 common section with conditional rendering based on Authorization Code grant type, rather than in the Authorization Code–specific section, centralizing related authentication configuration fields. ChangesOAuth2 Form Reorganization
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes 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)
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
Moves the "Authorization expires in (seconds)" field to appear right after the "Scope(s)" field in the OAuth2 datasource configuration form. This groups all authentication-related fields together for better UX.
Changes
renderOauth2AuthorizationCode()torenderOauth2Common()Fixes #31059
Summary by CodeRabbit