When the promise was rejected it took the error value and
set that as the value of the promise.
This lead to code expecting one shape to completely fail. This
now assigns the errorValue to an errorValue property on the
promise and the defaultValue to value when a promise is rejected.
rancher/rancher#24620
The downloaded report now has:
- A column for passed_nodes
- A column for failed_nodes
- A column for all nodes the test ran against
- The benchmark version in the header
rancher/rancher#24671
-We now prepopulate fields as select component instead of just
free-form text fields.
-We added support for cloning from different sources.
-We also added support for custom attributes and tags.
To implement the above features we also added support for promise
based content for new-select and search-select and created a new
component contextual-select-array which provides a method for
filtering content based on previous selections.
rancher/rancher#21580
- Moved from Ember.$() to importing jquery.
- Moved from fn().on() to on(fn())
- Moved from fn().observes() to observer(fn())
This got /g/clusters from 27 warnings to 5 warnings for me.
remove prototype extension
Remove translations from engines
The motivation behind this change stems from this issue ember-intl issues/797
and the current implmentation of engine support in ember-intl. The translations
essentially get bundled twice. Until ember-intl removes the second bundle it
makes sense to keep the translations in the main ui file.
Editing was failing when an existing unsupported storage type had
already been used and the ferature flag unsupported-storage-drivers
was false. Adding a volume as part of a workload was also broken
when attempting to use an unsupported storage type.
To remedy this I decided to refactor the code and make the filtering
happen explicitly only for the dropdowns.
I also decided to make feature checking reusable and either to use
by adding a service to check if a flag is enabled.
rancher/rancher#22895rancher/rancher#22998
Adds the resource types "namespace", "cluster", "project" as
additional context to the titles of the respective deletion modals
in order to reduce the likelyhood of a user accidentally deleting
an unintented resource.
We changed the title from "Are you sure you want to delete" to
"Are you sure you want to delete the namespace:" with namespace
being bold. The same is true for cluster and project as well.
rancher/rancher#17619
Cody Jackson
Westly Wright
Westly Wright
wj
n313893254
Cody Jackson
loganhz
Vincent Fiduccia
loganhz
Gábor Lipták