Content
View differences
Updated by Henriette Darge 2 days ago
##
##
## Purpose
Replace Storages::Admin::StorageListComponent's Storages::Admin::StorageListComponent's plain BorderBox/grid list with the shared semantic table, completing this deferred #DREAM-697 surface.
## Scope
Use OpPrimer::BorderBoxTableComponent and OpPrimer::BorderBoxRowComponent. Preserve the table/rowgroup/row/columnheader/cell semantics, accessible table name, column indices, mobile layout, and keyboard access to links and actions. This targets the existing ARIA table implementation; a native HTML table rewrite or new DataTable is outside this work.
Preserve name, creator, provider and creation-time columns, storage links, stable row identities, existing row actions and the empty-state content.
## Acceptance criteria
* [x] - [ ] Storage rows and column headers use shared table/row components with an accessible table name.
* [x] - [ ] Links, permissions, provider-specific rendering and any existing actions remain functional.
* [x] - [ ] Desktop/mobile presentation and empty-state behavior retain the information currently shown.
* [x] - [ ] Obsolete storage-list grid markup/styles are removed where superseded.
* [x] - [ ] Component and focused screen coverage verify semantics and user-visible behavior.
## Boundaries
Part of [DREAM-837](https://community.openproject.org/wp/DREAM-837). No manual ordering or column-sorting feature is introduced, and storage detail/settings boxes are outside this migration. Can proceed independently of [DREAM-838](https://community.openproject.org/wp/DREAM-838).
## Starting points
modules/storages/app/components/storages/admin/storage\_list\_component.{rb,html.erb} modules/storages/app/components/storages/admin/storage_list_component.{rb,html.erb} and storage\_row\_component.\*.
<br>
## Hint for QA
This can be tested on `/admin/settings/storages` . The table there should basically look and behave like before. storage_row_component.*.
##
## Purpose
Replace Storages::Admin::StorageListComponent's
## Scope
Use OpPrimer::BorderBoxTableComponent and OpPrimer::BorderBoxRowComponent. Preserve the table/rowgroup/row/columnheader/cell semantics, accessible table name, column indices, mobile layout, and keyboard access to links and actions. This targets the existing ARIA table implementation; a native HTML table rewrite or new DataTable is outside this work.
Preserve name, creator, provider and creation-time columns, storage links, stable row identities, existing row actions and the empty-state content.
## Acceptance criteria
* [x]
* [x]
* [x]
* [x]
* [x]
## Boundaries
Part of [DREAM-837](https://community.openproject.org/wp/DREAM-837). No manual ordering or column-sorting feature is introduced, and storage detail/settings boxes are outside this migration. Can proceed independently of [DREAM-838](https://community.openproject.org/wp/DREAM-838).
## Starting points
modules/storages/app/components/storages/admin/storage\_list\_component.{rb,html.erb}
<br>
## Hint for QA
This can be tested on `/admin/settings/storages` . The table there should basically look and behave like before.