-
Notifications
You must be signed in to change notification settings - Fork 17
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
Introducing bookmarks #1095
Introducing bookmarks #1095
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
Ow.. it's only when you are logged in?.. Makes since I guess. |
I fixed the minor points.
Answers:
|
|
|
dfd4d1e
to
61d6179
Compare
61d6179
to
945f70e
Compare
I addressed 1. but I am hesitent to implement 2. are you fine with letting the users decide whether they want 2. when this is released @melroy89 ? |
I think I'm with @BentiGorlich on this. I just checked, and even GitHub stars behave the same way; if you go to the star list in your profile and unstar one of the repositories, it still stays there until you actually reload the page (which works out in case you accidentally remove one of them). |
In this massive commit bookmarks are added. A user can create multiple bookmarking lists and add entries, posts and comments to them. They are all shown in one view when looking at the list. One point that is easy to miss: the caching of the twig components `EntryCommentsNestedComponent` and `PostCommentsNestedComponent` was removed (by not using the caching template). It is not really that useful (cache gets cleared as soon as anyone votes on it) and was getting in the way of rendering. That may later be reverted
- change route paths from `lists` -> `bookmark-lists` - when creating a default list because the user doesn't have one yet it will be called `Default` - add a title and aria-description to the start icon (default list) - make the header dropdown item be bold when it should be
- if one adds an item to the standard list the button for that specific list will update as well - if adding an item to a specific list the default item will be updated as well
45ea862
to
bbe1272
Compare
Aha. I see. To be honest don't compare UX with Github, since if some interface can be improved on planet earth it would be all Microsoft products including github. |
Sure. It's a minor UX issue I think. Mainly confusing I believe. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works!
Co-authored-by: Melroy van den Berg <melroy@melroy.org>
Co-authored-by: Melroy van den Berg <melroy@melroy.org>
Co-authored-by: Melroy van den Berg <melroy@melroy.org>
Co-authored-by: Melroy van den Berg <melroy@melroy.org>
Co-authored-by: Melroy van den Berg <melroy@melroy.org>
Co-authored-by: Melroy van den Berg <melroy@melroy.org>
Co-authored-by: Melroy van den Berg <melroy@melroy.org>
In this massive commit bookmarks are added. A user can create multiple bookmarking lists and add entries, posts and comments to them. They are all shown in one view when looking at the list.
UI
Add to default button
Entries, posts and comments now have a button to add a bookmark to the default bookmark list:
Add to list button
They all have the option to add them to a specific bookmark list in the dropdown menu:
Get to the list view
To get to the new view there is a new button in the profile dropdown:
The new list view
There is a new view for managing ones bookmark lists:
Looking at the content in a list:
When looking at the content of a bookmark list all types can be viewed simultaneously in the same list:
API
I already added the API, but it might not work correctly, as I didn't test it (might be possible to do so without an app to test it via test libs, but I didn't bother...)
There are some new scopes:
user:bookmark
,user:bookmark:add
,user:bookmark:remove
,user:bookmark:list
,user:bookmark:list:read
,user:bookmark:list:edit
anduser:bookmark:list:delete
. I do not know if I forgot a few places for them to be added thoughExtras
One point that is easy to miss: the caching of the twig components
EntryCommentsNestedComponent
andPostCommentsNestedComponent
was removed (by not using the caching template). It is not really that useful (cache gets cleared as soon as anyone votes on it) and was getting in the way of rendering. That may later be revertedCloses #46