Skip to content

Conversation

@afeld
Copy link
Contributor

@afeld afeld commented Apr 13, 2016

Closes #111.

At 18F, we often include something like the following in a project README:

To chat about this project, go to https://chat.18f.gov and select such-and-such from the dropdown.

Unfortunately, the latter direction often gets missed, and people end up joining the first channel listed. This pull request would allow the projects to link directly to their channel, avoiding the problem completely.

Instead of @mattgorecki's client-side solution, I opted to do the channel selection server-side so that they don't even see the dropdown:

screen shot 2016-04-12 at 11 27 24 pm

Let me know what you think!

/cc @konklone

let results = restrictChannels([], {query: {channel: 'foo'}});
assert.deepEqual(results, []);
});
});
Copy link
Contributor Author

Choose a reason for hiding this comment

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

These tests may seem overkill, but I was very nervous about creating a security hole where external users could join a channel that wasn't whitelisted through the channel list provided to slackin.

@afeld
Copy link
Contributor Author

afeld commented May 17, 2016

Bump!

@thom4parisot
Copy link

I'd be super happy to benefit from this feature. Likewise, we have a community of projects and people sign up for different reasons. I think it would benefit to their onboarding experience to reach the expected channel(s).

Is there anything to do to move this proposal forward?

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

Successfully merging this pull request may close these issues.

2 participants