No longer used.
This commit is contained in:
parent
c07ce445a0
commit
5e7dfcbd52
1 changed files with 0 additions and 21 deletions
21
guild.go
21
guild.go
|
@ -1,21 +0,0 @@
|
|||
package discordgo
|
||||
|
||||
/*
|
||||
TODO: How to name these? If we make a variable to store
|
||||
channels from READY packet, etc. We can't have a Channel
|
||||
func? And which is better. Channels func gets live up
|
||||
to date data on each call.. so, there is some benefit there.
|
||||
|
||||
Maybe it should have both, but make the Channels check and
|
||||
pull new data based on a cache time?
|
||||
|
||||
func (s *Server) Channels() (c []Channel, err error) {
|
||||
c, err = Channels(s.Session, s.Id)
|
||||
return
|
||||
}
|
||||
*/
|
||||
/*
|
||||
|
||||
func (s *Server) Members() (m []Users, err error) {
|
||||
}
|
||||
*/
|
Loading…
Reference in a new issue