- 
                Notifications
    
You must be signed in to change notification settings  - Fork 1.2k
 
UI: Fix duplicate quickview (for provider column) in backup repository #11849
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
UI: Fix duplicate quickview (for provider column) in backup repository #11849
Conversation
| 
           @sureshanaparti a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.  | 
    
          Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@            Coverage Diff            @@
##               main   #11849   +/-   ##
=========================================
  Coverage     17.56%   17.56%           
- Complexity    15542    15544    +2     
=========================================
  Files          5909     5909           
  Lines        529058   529058           
  Branches      64617    64618    +1     
=========================================
+ Hits          92922    92942   +20     
+ Misses       425683   425660   -23     
- Partials      10453    10456    +3     
 Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
  | 
    
| 
           UI build: ✔️  | 
    
| 
           @DaanHoogland that will enable quick view only in oauthsetting, for provider column. all other views have name column and route is not oauthsetting. name column is the usual quick view column, only exception is provider column (used in oauthsetting for quick view)  | 
    
235d726    to
    8e0dc34      
    Compare
  
    
          
 Thanks @sureshanaparti , I had found my erroneous way of thinking and deleted my comment.  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
8e0dc34    to
    d0a5207      
    Compare
  
    d0a5207    to
    ac63e7e      
    Compare
  
    | 
           @sureshanaparti a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.  | 
    
| 
           UI build: ✔️  | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sureshanaparti The provider column was still showing the quick view with these changes in backup repository.
I have suggested a change in quickViewEnabled(). Can we keep the check that the column has to be the first column? Also can we remove all checks regarding column names (name, provider, hypervisor etc)? These are already being checked before calling quickViewEnabled in the parent elements.
| return actions.length > 0 && | ||
| (columns && ['name', 'provider', 'hypervisor', 'intervaltype'].includes(columns[0].dataIndex) || ['displayname'].includes(key)) && | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| return actions.length > 0 && | |
| (columns && ['name', 'provider', 'hypervisor', 'intervaltype'].includes(columns[0].dataIndex) || ['displayname'].includes(key)) && | |
| return actions.length > 0 && key == columns[0].dataIndex && | 


Description
This PR fixes duplicate quickview (for provider column) in backup repository, and consolidates the existing quickview for first column, column key.
Quickview for provider column is enabled for OAuth providers only, here: https://github.com/apache/cloudstack/pull/7996/files#diff-fa50e9f30df1f49ab46e9e30d15009ff36b166ce26cb289a8ec75a4f60873d2b
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Primarily verified quick views for the below sections in UI, randomly checked few other sections as well.
Backup Repository UI, Before Fix:
Backup Repository UI, After Fix:
OAuth Configuration UI, No change:
How did you try to break this feature and the system with this change?