UI: fixes pki role editing changing to default key parameter values #20907
+135
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes a bug that reset
key_bits
andsignature_bits
when editing a pki role.This was happening because the type coming back from the API is an integer but the dropdown options for these params are strings (the API accepts both types). This means the
<select>
element's selected conditional fails because the values don't initialize as the same type:We're unable to update the option list to be integers because as soon as an option is selected it becomes a string type. See below,

Key bits
hasn't been edited and is an integer (from the API).Signature bits
has been changed in the UI using the dropdown and is now a string:I also attempted to make a custom transform, however this model uses
openApi
and the attributetype
is overwritten and therefore won't hit thedeserialize
orserialize
methods in a custom transform