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 support for banlist messages #1009

Merged
merged 1 commit into from Apr 22, 2017
Merged

Add support for banlist messages #1009

merged 1 commit into from Apr 22, 2017

Conversation

AlMcKinlay
Copy link
Member

Fixes #1008

@MaxLeiter
Copy link
Member

is it common to push to lobby? not to the channel the command is being called?

@xPaw
Copy link
Member

xPaw commented Apr 4, 2017

Could use the special Chan type, same as /list.

@AlMcKinlay
Copy link
Member Author

is it common to push to lobby? not to the channel the command is being called?

In my experience, most IRC clients only push to the channel if it is a message directly.

I mean, ideally we would want to show a modal or something, with buttons to remove from the banlist, but this is just a first version so that we support it at all.

Could use the special Chan type, same as /list.

I guess we could, yeah.

I think the thing is we don't want to end up just everything being a channel, because then we will end up not doing it in a nicer way, as we are a web app and we want to do things nicely for the user, not just in the simplest way possible.

But if you think that's the best thing to do for this first version, then I'm happy to do that.

@AlMcKinlay
Copy link
Member Author

Well, I've pushed a commit to have a special chan for banlist entries. I'm not using any special message format (like the chanlist is). It's probably best if I do, and I pass the other information through to the client for showing.

For reference, this is what we get back from the server:

[ { channel: '#channelthatdoesntexist',
    banned: 'test!*@*',
    banned_by: 'ymk2!~ymk2@29.93.2.81.in-addr.arpa',
    banned_at: '1491320726' } ]

So it's probably worth showing the banned by and the banned at. I'll add that. See what you think about this.

@astorije
Copy link
Member

astorije commented Apr 7, 2017

@YaManicKill, mind adding an entry in the "commands" section of the help window, between /back and /ctcp?

@AlMcKinlay
Copy link
Member Author

Alright, I have completely changed this.

Now it is a custom chan with custom messages, basically the same as how /list works, but obviously showing useful information for the banlist.

/banlist also wasn't a command we supported, so I added that so people don't have to remember the correct mode.

I have also added /banlist to the help section, as requested.

It works quite nicely now, I think.

Copy link
Member

@astorije astorije left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's really cool, @YaManicKill! I just tested quickly and didn't look at the code at all yet, but the result is 👌. I'll give it a proper review sometime soon.

Mind rebasing on master to take into account the recent changes to special channels by #1018?

@AlMcKinlay
Copy link
Member Author

Mind rebasing on master to take into account the recent changes to special channels by #1018?

Yeah, I'll do that soon.

@AlMcKinlay
Copy link
Member Author

Rebased onto master, and using the new stuff from #1018.

@AlMcKinlay AlMcKinlay force-pushed the yamanickill/1008-banlist branch 3 times, most recently from 0c48ac7 to a77e007 Compare April 21, 2017 08:57
Copy link
Member

@astorije astorije left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good job!

@astorije astorije added the Type: Feature Tickets that describe a desired feature or PRs that add them to the project. label Apr 22, 2017
@astorije astorije added this to the 2.3.0 milestone Apr 22, 2017
@astorije
Copy link
Member

@YaManicKill just so you know I didn't make any changes but when I wanted to test I got that undefined bug back so I rebased with master to be able to test then figured I might as well send that up-to-date version.

Copy link
Member

@xPaw xPaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving, but please add /banlist to client's autocompletion list.

@AlMcKinlay
Copy link
Member Author

Alright, I have added the command to the autocompletion list, and I have rebased and squashed. I think this is good to go now, then,

@xPaw xPaw merged commit 78221fc into master Apr 22, 2017
@xPaw xPaw deleted the yamanickill/1008-banlist branch April 22, 2017 13:22
@astorije astorije mentioned this pull request Apr 22, 2017
matburnham pushed a commit to matburnham/lounge that referenced this pull request Sep 6, 2017
@xPaw xPaw removed their assignment Mar 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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.

None yet

4 participants