a4fe656d0d
Separating tabs of single panel to separate panels. It will reduce amount of redundant calls, because it is very unlikely that someone will need all tabs at once. Also, it is current approach that is used by core projects. Similar refactor for admin dashboard is located at [1] [1] I874253e0e9a35ede8239bc1bdf0a330a44ade413 Change-Id: Ia8a432e136a9c06f3db887b9289d90853dd027e6 Partially-Implements BluePrint create-share-panel-group
13 lines
571 B
YAML
13 lines
571 B
YAML
---
|
|
features:
|
|
- Project dashboard now has manila-specific panel group called 'share'.
|
|
All 'tabs' we had before are panels in this group now. Each panel
|
|
is loaded in separate page. It allows us to avoid making redundant
|
|
API calls that we did loading all tabs at once.
|
|
upgrade:
|
|
- URLs for resources in project dashboard were changed.
|
|
One part of changes is removal of intermediate "shares" part. Example -
|
|
was - "/project/shares/share_networks/"
|
|
became - "/project/share_networks/"
|
|
Other part is rename of resource actions to be more alike.
|