Conversation
Removed unnecessary spacing and section regions to streamline the form. These elements were redundant in simple pages where there is no need to distinguish between different sections or content.
This change is a step toward having forms display only "required" inputs. While not yet documented in developer guidelines, it has been discussed and agreed that forms should show only required inputs or inputs that will always have a value. Optional fields should be explicitly requested by the user, effectively making them required once displayed. In the registration form, this applies to the email input: if the user does not select "Provide email address," the email input field is neither rendered nor validated. However, if selected, it is displayed and validated accordingly.
The idea is to make it easier for users to set a hostname when registering a product, as the product will be registered with the specified hostname. Instead of adding warnings elsewhere, it’s more helpful to let users set the hostname directly from the registration form too, which will be prefilled with the current hostname value. NOTE: This commit only updates the interface. The logic for setting the hostname is not yet implemented. Tests are intentionally broken to prevent overlooking it.
This commit adds only the basic interface components. Logic for setting the hostname and its options still pending to be implemented.
Alert users that changing the hostname of an already registered product will not update the hostname used during registration.
|
After separate discussions with @teclator and @imobachgs, the following changes are planned:
Thus, below changes will be performed for considering this PR ready
|
On the registration page, the hostname input is replaced with an alert to provide helpful information to users about hostname implications during registration, without giving the impression that it can be updated later.
And more unit testing.
The option to enable DHCP hostname is removed since it will not be implemented by now. This commit also includes additional unit tests, which are intentionally broken to serve as a reminder to update them once the actual hooks are implemented.
By adding hte missing pieces for communicating with the server.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Pull Request Test Coverage Report for Build 13856030764Details
💛 - Coveralls |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
imobachgs
left a comment
There was a problem hiding this comment.
The code looks good. However, the wording might be improved.
There was a problem hiding this comment.
I need help for fix it. I do not have an idea of a good text for helping users there. I'm a bit lost with transient and static stuff. So, I hope @teclator (or anyone else) can help me with it.
There was a problem hiding this comment.
After a chat with @teclator I realize that actually it was desired to allow the user unset the static hostname too. Thus, the form has changed a bit and this explanation now belongs to a checkbox in which a final sentence has been added. Unless somebody suggest something better.
Co-authored-by: Imobach González Sosa <igonzalezsosa@suse.com>
For using real useHostname hook and display the proper hostname value to users.
Introduces a custom alert at the top of the hostname page to provide users with both the current hostname value and the mode (permanent or temporary). The goal is to ensure users not only know the current hostname but also understand the meaning and implications of each mode, helping them make an informed choice. While there’s room for improvement, further refinements will be addressed in future updates when moving toward a system page. This will help unblock the current work and enable users to set the hostname via the web interface as soon as possible.
|
@teclator, re-ready for a review. @imobachgs ^^^ (just in case this still opens when you are back. Hope it will not). |
Override PatternFly styles to ensure that a FormGroup aligns to the start of its flex container instead of stretching to fill all available space by default. https://developer.mozilla.org/en-US/docs/Web/CSS/justify-content#normal
Among others (out of the scope of the feature this commit belongs), storage/EncryptionSettingsPage form no longer requires individual tweaks to prevent fields from stretching to match the widest one.
To make them a bit more bigger.
Suggested by @teclator in an "pair-review" session.
|
Swedish translation for this updated |
The registration form was updated in PR #2147 to make the email field optional, neither rendering nor validating it unless the user opts to provide an email address. However, the process was failing silently due to the backend complaining about a malformed JSON. > Failed to deserialize the JSON body into the target type: missing > field `email` at line 1 column 16 This commit fixes the issue by sending the email as an empty string when the user chooses not to provide it.
The registration form was updated in PR #2147 to make the email field optional, neither rendering nor validating it unless the user opts to provide an email address. However, the process was failing silently due to the backend complaining about a malformed JSON. > Failed to deserialize the JSON body into the target type: missing > field `email` at line 1 column 16 This PR fixes the issue by sending the email as an empty string when the user chooses not to provide it.
Prepare for releasing Agama 13: - #2041 - #2074 - #2088 - #2089 - #2094 - #2097 - #2098 - #2100 - #2101 - #2104 - #2106 - #2107 - #2108 - #2113 - #2115 - #2116 - #2117 - #2118 - #2120 - #2121 - #2122 - #2123 - #2124 - #2125 - #2126 - #2128 - #2132 - #2135 - #2136 - #2137 - #2139 - #2142 - #2145 - #2146 - #2147 - #2148 - #2151 - #2153 - #2155 - #2156 - #2157 - #2158 - #2159 - #2160 - #2161 - #2163 - #2165 - #2172 - #2174 - #2177 - #2179 - #2180 - #2181 - #2182 - #2183 - #2184 - #2186 - #2187 - #2188 - #2191 - #2192 - #2193 - #2195 - #2197 - #2198 - #2199 - #2200 - #2201 - #2203 - #2204 - #2205 - #2206 - #2207 - #2209 - #2212 - #2213 - #2214 - #2215 - #2216
Problem
Currently, users cannot edit the hostname through the web user interface.
Solution
Add a page that allows users to change the hostname directly from the web UI. Additionally, warn users at the registration form about hostname implications with a link to the section for changing it.
Tests
Notes
lvm-formbranch to make forms looks a bit better. The motivation to do so is: a) LVM PR is taking longer than expected; b) this PR is no longer against a temporary branch but againstmasterScreenshots
Related to https://trello.com/c/bDToEZ43 (protected link)