Closed Rapptz closed 7 years ago
I vote Guild
as it's consistent with API terminology
i think that guilds makes sense because it's how the official refers to it.
I vote server because I don't think we should fix something that isn't broken
I'd go for Guild
because it'd match how the API refers to it
Guild
, thanks.
I vote for Guild, keep the library consistent with how Discord itself calls it.
As much as I dislike the word, guild
for consistency with the API
Guild
.
Guild
it is gonna be biggest break change for covert server object to guild lol
Server
, this will be the biggest search and replace I'd have to do if renamed...
@NotSoSuper It's for a rewrite, you'll have to rewrite most of your code anyways.
As much as I hate the Guild structure, a wrapper should mirror what it abstracts. So Guild here too.
guild
and server
@Helehelehele how so? Afaik he's only changing the server class name to guild.
@NotSoSuper The entire lib is going through a rewrite
@NotSoSuper see https://github.com/Rapptz/discord.py/milestone/5
thanks, was unaware of that.
I'm team 'server'.
As evoked in discord, the permissions have different names too, "Manage Server" vs "Manage Guild", etc. As much as being consistent with the api is nice, being consistent with the UI and what people are used to see feels more right.
Only people that are used to discord's docs might get confused, others will look at this lib's docs and never even know they have a different name.
If you go the "api consistency" way, I can already feel the "how do I check if someone has the manage server permission???" coming.
I'd go with Guild as well.
@PapyrusThePlant you can't cure ignorance. People get into d.py channel without knowing any programming languages. They are the ones who need to adapt, not the lib.
Guild
would be nice
I'm going with Server. I agree with Papyrus.
My 2 cents even though I just started... 'Server'
In the end, it doesn't really matter all that much. IF the decision is made to go with 'guild' then I'd suggest the reverse of the item above... "Note: the discord UI refers to guilds as servers"
I vote Guild
for consistency :smile:
I'd have to vote Guild
too, as it's what the documentation and actual CSS use. I dislike the use of the word internally as I feel they're still servers, but feel it makes more sense from the official API point of view.
+1 for Guild
from me
Following the majority.
Screw it. Guild
.
If it's not too late, discord.js switched from Server to Guild between version 8 and 9
discord.py isn't discord.js
Abal I know but I thought it might help Danny as most of our users didn't care too much that it changed, he may choose to leave it the same for the sake of backwards compatibility but I believe he might as well change it now
abal stop
Sorry hope my further comment cleared it up
I already changed it to guild in the rewrite I have locally.
At the moment the API wrapper calls what the API internally calls "guilds" as "servers" due to the UI association with a "guild" being called a server. This is a left over from the library being written as a reverse engineer attempt from the beginning.
Should
Server
and all instances ofserver
be renamed toGuild
andguild
respectively to be more consistent with the API terminology?You cannot have both naming schemes and I'm only going to count votes from this issue.