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: 802.1x tab displaying and refresh #5055

Merged
merged 2 commits into from
Dec 12, 2023
Merged

fix: 802.1x tab displaying and refresh #5055

merged 2 commits into from
Dec 12, 2023

Conversation

MMaiero
Copy link
Contributor

@MMaiero MMaiero commented Dec 12, 2023

Note: We are using the Conventional Commits convention for our pull request titles. Please take a look at the PR title format document for the supported types and scopes.

Brief description of the PR. [e.g. Added null check on object to avoid NullPointerException]

Related Issue: N/A

Description of the solution adopted: Another attempt to improve the availability and refresh for the 802.1x tab in the wireless section

Screenshots: N/A

Manual Tests: Tested with ipv4 and ipv6 disabled as well enabling each of them. All the tests done first without and then with the selection of the enterprise security.

Any side note on the changes made: N/A

@MMaiero MMaiero requested a review from mattdibi December 12, 2023 08:47
@mattdibi
Copy link
Contributor

mattdibi commented Dec 12, 2023

Disabled parameters initialization

After first opening the tab the field are disabled as expected

Before this PR:

image

After this PR:

image

Note: both screenshot were taken upon first opening the 802.1x tab in Kura

802.1x tab enabling

802.1x tab is correctly enabled when either one (or both) between ipv4 and ipv6 is enabled and the wireless security is set to WPA Enterprise.

Comment on lines 356 to 360
logger.info("update");
setValues();
refreshForm();
this.netTabs.updateTabs();
logger.info("update... done");
Copy link
Contributor

Choose a reason for hiding this comment

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

Only thing here is... is this log entry worth the info level or would it be better suited for the debug level?

Suggested change
logger.info("update");
setValues();
refreshForm();
this.netTabs.updateTabs();
logger.info("update... done");
logger.debug("update");
setValues();
refreshForm();
this.netTabs.updateTabs();
logger.debug("update... done");

@@ -370,6 +382,7 @@ private void refreshForm() {
}

private void reset() {
logger.info("reset");
Copy link
Contributor

Choose a reason for hiding this comment

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

Same here

Suggested change
logger.info("reset");
logger.debug("reset");

@@ -390,6 +403,8 @@ private void reset() {
this.keystorePid.setValue("");
this.caCertName.setValue("");
this.publicPrivateKeyPairName.setValue("");
update();
logger.info("reset... done");
Copy link
Contributor

Choose a reason for hiding this comment

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

... and here

Suggested change
logger.info("reset... done");
logger.debug("reset... done");

Signed-off-by: MMaiero <[email protected]>
@MMaiero
Copy link
Contributor Author

MMaiero commented Dec 12, 2023

@mattdibi I have removed the logs.

@MMaiero MMaiero merged commit f978be3 into develop Dec 12, 2023
3 checks passed
@MMaiero MMaiero deleted the fix_8021x_refresh branch December 12, 2023 14:34
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