-
Notifications
You must be signed in to change notification settings - Fork 62
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
Collapse extended options wizard #1609
Collapse extended options wizard #1609
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kgroschoff The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report
@@ Coverage Diff @@
## master #1609 +/- ##
==========================================
- Coverage 71.57% 71.52% -0.06%
==========================================
Files 210 222 +12
Lines 6818 7164 +346
Branches 682 712 +30
==========================================
+ Hits 4880 5124 +244
- Misses 1671 1764 +93
- Partials 267 276 +9
Continue to review full report at Codecov.
|
/hold |
/hold cancel |
45b445b
to
88538c2
Compare
@@ -0,0 +1,3 @@ | |||
.km-tags-in-wizard { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If it works for all kind of tags then can we move to the main app.scss?
key: new FormControl(''), | ||
value: new FormControl(''), | ||
})); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use a separate function for tag list initialization?
} else { | ||
this.azureNodeForm.controls.size.enable(); | ||
this.form.controls.size.enable(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
</div> | ||
|
||
<div class="km-form-group-tags-header"> | ||
Tags |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do the tags for Azure and for example AWS work in the same way? This is not the scope of this PR but we could do it in another one and it would reduce code duplication a bit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes and I'd like to style them similar to e.g. Node Labels. So probably a new component for Provider Tags, but I'd like to do this in a seperate PR, as this also will be a bigger PR.
key: new FormControl(''), | ||
value: new FormControl(''), | ||
})); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we separate to another method?
88538c2
to
c236cf3
Compare
@maciaszczykm PTAL :) |
eb1cfa2
to
aed130b
Compare
@maciaszczykm I resolved the merge conflicts. PTAL |
@kgroschoff Sorry, for the delay... I am looking on it right now. |
/lgtm Great work 👏 |
LGTM label has been added. Git tree hash: a0987f1be79f41ebce045b2c285228abc7ef33d7
|
What this PR does / why we need it:
Add possibility to collapse extended options & restructure order,
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #1518
Special notes for your reviewer:
Sorry for this huge PR 😞
I would suggest to use the same styling for Provider Tags as vor Node Labels. But as this will be definitely too much for this PR, I'd keep this as seperate issue.
Extremely short overview:
SetSettingsComponent
includesExtendedOptionsComponent
ExtendedOptionsComponent
includesClusterProviderOptionsComponent
&NodeDataOptionsComponent
Example AWS:
Release note: