blizzz
commented
2 months ago So on the backend side we have things in place, but disabled. To turn it on, we simply need:
On the frontend side we need
- [ ] a control for the context owner to set the default display mode.
- [ ] a control per context for a user to set a personal overwrite (e.g. hide or enable)
For the record, we have three modes. The constants are define in Application:
public const NAV_ENTRY_MODE_HIDDEN = 0;
public const NAV_ENTRY_MODE_RECIPIENTS = 1;
public const NAV_ENTRY_MODE_ALL = 2;- NAV_ENTRY_MODE_HIDDEN - no nav bar entry
- NAV_ENTRY_MODE_RECIPIENTS - nav bar entry for share recipients, but not the owner
- NAV_ENTRY_MODE_ALL - nav bar entry for everybody
Setting the Nav bar entry is possible via following routes:
api1#updateShareDisplayModeshare#updateDisplayMode
as well as when creating a share, via optional displayMode mode parameter. Default is hidden!
UPDATE 2024-07-26
For we have started to show applications by default, while the nominal default would be to hide them, we also shall change the default to show all and have a repair step to update the existing applications. So, users will not be confused while their applications are not there anymore, also it may be a better, more discoverable setting.
- [ ] change default from NAV_ENTRY_MODE_HIDDEN to NAV_ENTRY_MODE_ALL – https://github.com/nextcloud/tables/pull/1250
- [ ] add repair step to change all existing settings in the database from NAV_ENTRY_MODE_HIDDEN to NAV_ENTRY_MODE_ALL – https://github.com/nextcloud/tables/pull/1250
juliushaertl
enjeck
Leftover from contexts work.
@blizzz Could you document the current logic on what is possible for hiding the applications from the backend side in here so we can have a clear description on what we need to do on the frontend?