Skip to content

Conversation

@lucas-a-martins
Copy link
Collaborator

@lucas-a-martins lucas-a-martins commented Mar 20, 2025

Description

Currently, the only way to update a value in the resource settings tabs is by typing the new value as a text, regardless of its type (boolean, range, percentage, etc).

This PR change this behavior to work like the global settings, where the edition is based on the value type.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)
  • build/CI
  • test (unit or integration test code)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

Screenshots (if appropriate):

Screenshot from 2025-03-18 17-50-25

How Has This Been Tested?

I tested it by accessing each affected settings tab to confirm that the changes were applied.

I also changed some configurations values to see if everything still works as intended.

@codecov
Copy link

codecov bot commented Mar 20, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 16.29%. Comparing base (1c1dad9) to head (358d503).
Report is 43 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #10596      +/-   ##
============================================
+ Coverage     16.17%   16.29%   +0.12%     
- Complexity    13291    13437     +146     
============================================
  Files          5668     5674       +6     
  Lines        498179   499203    +1024     
  Branches      60290    60368      +78     
============================================
+ Hits          80581    81368     +787     
- Misses       408578   408765     +187     
- Partials       9020     9070      +50     
Flag Coverage Δ
uitests 3.99% <ø> (+<0.01%) ⬆️
unittests 17.15% <ø> (+0.13%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@bernardodemarco
Copy link
Member

@blueorangutan ui

@blueorangutan
Copy link

@bernardodemarco a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

@blueorangutan
Copy link

UI build: ✔️
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/10596 (QA-JID-581)

Copy link
Contributor

@DaanHoogland DaanHoogland left a comment

Choose a reason for hiding this comment

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

lgrm, tested in qa

Copy link
Member

@bernardodemarco bernardodemarco left a comment

Choose a reason for hiding this comment

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

lgtm, nice work @lucas-a-martins

Tested updating and resetting configuration values, and filtering settings by name

@bernardodemarco bernardodemarco added this to the 4.21.0 milestone Mar 27, 2025
@DaanHoogland DaanHoogland merged commit 8d18c1e into apache:main Mar 28, 2025
24 of 25 checks passed
dhslove pushed a commit to ablecloud-team/ablestack-cloud that referenced this pull request Jun 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

No open projects
Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants