nextcloud / nextcloud/collectives

Dismiss button for "folder content best viewed in collectives app" header in file list

Open
#591 11 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: attachments
Dominant language
JavaScript
Stars
195
Forks
51
Avg merge
1d 2h
Merged PRs (30d)
48

Description

Browsing a folder which belongs to a collective in the files app shows a message "The content of this folder is best viewed in the Collectives app." on top of the file list.

Allow to dismiss the info header in the file list. It should be a persistent change for the user.

Background

For our use case most content (e.g. the files displayed in that folder) is currently not displayed from within the collectives app.

I assume this message is intended for users that only (automatically) store the collective "wiki style" markdown pages in the folder hierarchy below Collectives/collective_name.

However the automatically created folder Collectives/collective_name can be used for normal "file sharing" within the collective as well - and in that case, above message doesn't make much sense - as here, the content of this folder is not best viewed in the Collectives app, because it doesn't display relevant parts of the folder.

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

Start by locating the file-list UI that renders the “The content of this folder is best viewed in the Collectives app.” header for folders under Collectives. Trace how user-specific preferences are persisted, then verify that dismissing the header hides it for that user on subsequent visits while leaving other users unaffected.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.