Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide technical endpoints in the WidgetManager’s widget screen #68

Closed
KralMar opened this issue Aug 30, 2019 · 6 comments
Closed

Hide technical endpoints in the WidgetManager’s widget screen #68

KralMar opened this issue Aug 30, 2019 · 6 comments
Milestone

Comments

@KralMar
Copy link
Contributor

KralMar commented Aug 30, 2019

Currently a user always sees all endpoints he has access to, even the default ones.
This leads to a huge bloat of the Widgetmanager.

Steps to reproduce:

  • Fresh install of core4
  • Create a user with standard_user permissions
  • Log in
  • The WidgetManager shows “widgets” like LogoutHandler, LoginHandler, AccessHandler, … that the user is not interested in.

Suggested behaviour:

  • “Technical Endpoints” are hidden by default and can be made visible.

Next Steps:

  • Draft and align solution alternatives
  • Decide whether to accept the suggested behaviour or suggest a different one.
  • Qualify existing core4os endpoints if they are technical/non-technical
@KralMar KralMar added this to the release 0.4.0 milestone Aug 30, 2019
@marekmru
Copy link
Contributor

Technical endpoints can be identified by the tag "api".

@m-rau
Copy link
Contributor

m-rau commented Sep 2, 2019

this "api" tag is also the default tag if the developer does not define his own tags.

@marekmru
Copy link
Contributor

marekmru commented Sep 2, 2019

step1
step2
Please review the proposition for a solution.
The menu solution can be easily extended for more features and it does not interfere with users task. @m-rau

@marekmru marekmru assigned marekmru and m-rau and unassigned marekmru Sep 2, 2019
@m-rau
Copy link
Contributor

m-rau commented Sep 2, 2019

My guess is that

  1. all features we discuss here are related to the search
  2. all features not related to the search might be into the top-most menue

Therefore my input is: if this "menu" is search related, why not locate the menu inside the search text field!?

@m-rau m-rau assigned marekmru and unassigned m-rau Sep 2, 2019
@marekmru
Copy link
Contributor

marekmru commented Sep 3, 2019

Resolved in #76

@marekmru marekmru assigned m-rau and unassigned marekmru Sep 3, 2019
@m-rau m-rau removed their assignment Sep 3, 2019
@m-rau
Copy link
Contributor

m-rau commented Sep 3, 2019

to be reviewed in the merge into develop. Ticket closed.

@m-rau m-rau closed this as completed Sep 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants