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

Add favoriting/pinning channels #4556

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Add favoriting/pinning channels #4556

wants to merge 3 commits into from

Conversation

MaxLeiter
Copy link
Member

@MaxLeiter MaxLeiter commented May 1, 2022

Closes #180, #4078(?)

It effectively adds a new network, 'favorites' that can contain channels from any network.

If there's a name conflict, the server name is appended to the channel name while it's favorited.

The functionality all works except the command, as I'm not sure of how that should work.

I was thinking:

/favorites add [target] [...targets]
/favorites remove [target] [...targets]
/favorites clear

If no target is provided, it's assumed to be the current channel.

Here you can see two #testing123 channels with the server name attached. It's also added to the topic line, so (for example) on mobile you can be confident which you pressed
A screenshot showing the Favorites 'network'

The Favorites 'network' can't be opened (clicking it does nothing), but does have a context menu:
The context menu has one option: 'clear favorites'

You can add channels/queries to your favorites with the context menu (or aforementioned command):
Context menues have an 'add to favorites' option now

@MaxLeiter MaxLeiter added the Type: Feature Tickets that describe a desired feature or PRs that add them to the project. label May 1, 2022
@MaxLeiter MaxLeiter added the Status: needs-review PR not yet reviewed by enough maintainers label May 1, 2022
@xPaw
Copy link
Member

xPaw commented May 1, 2022

The functionality all works except the command, as I'm not sure of how that should work.

Sounds like the channel object should know which network it belongs to, so it should just work™.

@MaxLeiter
Copy link
Member Author

MaxLeiter commented May 1, 2022

@xPaw I meant the command interface:

I was thinking:

/favorites add [target] [...targets]
/favorites remove [target] [...targets]
/favorites clear

The alternative is
/favorite [target]
/unfavorite [target]
and not sure how clear would look

@xPaw
Copy link
Member

xPaw commented May 1, 2022

Ah right, misunderstood.

The (un)favorite syntax would match all the existing commands.

@igalic
Copy link
Contributor

igalic commented May 1, 2022

it's always possible to have those be aliases
some people may find the first more intuitive and others the second

i for instance add aliases in git for tags, branches and remotes, which by default print those in a sensible (to me) format

@itsjohncs
Copy link
Member

I'd give a vote for unfavorite and favorite. I think subcommands are nice as a way to do namespacing when there's a really huge number of commands (like git), but that's not the case here.

@brunnre8
Copy link
Member

Let's go for consistency and /favorite + /unfavorite then? Or what's the consensus now?

@fnutt
Copy link
Contributor

fnutt commented Jan 23, 2023

I agree about /favorite and /unfavorite. 👍 Good work @MaxLeiter!

@fionera

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: needs-review PR not yet reviewed by enough maintainers Type: Feature Tickets that describe a desired feature or PRs that add them to the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Favourite/Unified channels list
7 participants