nextcloud / nextcloud/tables

Improve Tables List

Open
#2,382 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
JavaScript
Stars
214
Forks
52
Avg merge
1d 10h
Merged PRs (30d)
82

Description

Is your feature request related to a problem? Please describe.

If i have access to an application the views contained in this Application will also be listed in Tables-App. All views contained within Applications i have access to, are now shown in my list of Tables in Tables App. This gets realy crowded fast, without any visual representaion or distingtion between tables and views that are shared with me. Neither in wich fassion (Application / directly) their are shared with me or their relations to each other.

Describe the solution you'd like

Copy the behaviour of calendar App. This would wastly improve usability and keep UI across multiple Apps consistent.
Three new Riders (currently their are Tables and Applications) "Tables shared with you", "Applications shared with you" and "Hidden". Also the User that shared the view and/or owns the table and or view should be represented in the list. Calendar does this by showing the name of the originating Account and its Profilepicture behind the name of the Calendar - same could be done for tables/views. And finally the option to hide tables and/or Views same as Calendar app does it.
Additionaly it would be great if Tables that are shared with me could be nested beneath the tables they originate from. Instead of the originating table only the "Views" Part can be rendered for the views accessible.

Describe alternatives you've considered

No response

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by comparing the Tables list with Calendar's shared and hidden-item behavior, then define the UI and data changes needed for separate shared and hidden sections, ownership details, nesting, and hiding; done means these relationships and controls are represented consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.