Skip to content
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

Fix unexpected default nics dropdown item when creating network configuration #7

Merged
merged 1 commit into from
Oct 22, 2024

Conversation

a110605
Copy link
Contributor

@a110605 a110605 commented Oct 22, 2024

Due to :defaultAddValue was added in this commit, the default selected item will be option[0].value even option[0].disabled = true which doesn't make sense to me.

With torchiaf/dashboard#7 change, we can have same behavior in harvester/dashboard

Current behavior
Screenshot 2024-10-22 at 1 38 58 PM

After fix

aaa.mov

@a110605 a110605 changed the title Fix unexpected Nics dropdown when creating network configuration Fix unexpected default nics dropdown items when creating network configuration Oct 22, 2024
@@ -361,21 +361,6 @@ export default {

this.nicErrors = uniq(nicErrors);
},

'value.spec.uplink.nics'(nics = []) {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

We don't need to show warning banner after selected nic. Since disabled options cannot be selected.

@a110605 a110605 changed the title Fix unexpected default nics dropdown items when creating network configuration Fix unexpected default nics dropdown item when creating network configuration Oct 22, 2024
Copy link
Owner

@torchiaf torchiaf left a comment

Choose a reason for hiding this comment

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

LGTM

@torchiaf torchiaf merged commit 16688bd into torchiaf:main Oct 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants