* fix: setup new routes
* fix: copy toggle
* fix: link to correct project
* fix: redirect oss to default
* fix: update tests
* fix: edit path
* fix: remove invalid property
* fix: add project to test data
* fix: update paths to use features
* fix: update test data
* fix: update snapshots
* fix: only show button to add toggle if you have access
* fix: change heading
* fix: use new route
* fix: archive view
* fix: update snapshots
* fix: sorting headers
* fix: list headers
* fix: only show span if revive is present
* fix: add border to list
* fix: update snapshots
* fix: remove console log
* fix: remove project display check
* fix: refetch bootstrap on user change
* fix: remove console log
* fix: update test
* fix: do not allow submit if errors exists
* fix: do not allow strategies to redirect home when name is taken
Co-authored-by: Ivar Conradi Østhus <ivarconr@gmail.com>
Co-authored-by: Christopher Kolstad <chriswk@getunleash.ai>
Co-authored-by: Christopher Kolstad <git@chriswk.no>
Create a new feature toggle by cloning the config of an
existing feature toggle.
This feature alos moves away from the input store for the
"create feature toggle form".
Because we convert items from Immutable Object to js
we can not just look up items in a list property via
the object itself, as it is not the same.
The easy fix is to just use the index of the item in
the list, as we already know it anyway.
closes#5