Skip to content
This repository has been archived by the owner on Jul 16, 2022. It is now read-only.

[Suggestion] Use vanity URL for partnered servers for public listing #161

Open
vladfrangu opened this issue May 29, 2017 · 2 comments
Open
Assignees
Labels
target: Web Issues that target GAB's Web Server type: Enhancement Issues that enhance an existing feature or module

Comments

@vladfrangu
Copy link
Member

That way, we don't make unnecessary invites for partnered servers!

@vladfrangu vladfrangu added type: Enhancement Issues that enhance an existing feature or module target: Web Issues that target GAB's Web Server labels May 29, 2017
@Gilbert142
Copy link
Member

Good idea, will push on v4.0.2 or v4.0.3

@Gilbert142 Gilbert142 added this to Planned / Confirmed in Information Board Oct 13, 2017
@vladfrangu vladfrangu moved this from Planned / Confirmed to High Priority / Next Patch in Information Board Dec 6, 2017
@vladfrangu
Copy link
Member Author

vladfrangu commented Feb 20, 2018

Endpoint: GET /guild/id/vanity-url
Requires the bot to have manage guild, so rather, we'd make server admins choose between giving gab manage guild to check the vanity url OR make them manually enter it and then use client.fetchInvite to see where it goes, invalid inv / wrong guild => error

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
target: Web Issues that target GAB's Web Server type: Enhancement Issues that enhance an existing feature or module
Projects
Information Board
  
High Priority / Next Patch
Development

No branches or pull requests

2 participants