constant

const DiscordVersion = 6

DiscordVersion API version

const DisgordTestBot = "DISGORD_TEST_BOT"

DisgordTestBot bot token for a disgord testing bot

const DisgordTestGuildAdmin = "DISGORD_TEST_GUILD_ADMIN"

DisgordTestGuildAdmin A guild snowflake id where the bot has administrator permission

const DisgordTestGuildDefault = "DISGORD_TEST_GUILD_DEFAULT"

DisgordTestGuildDefault Guild snowflake id where the default discord permission assigned when joining a vanilla guild

const DisgordTestGuildDefaultEmojiSnowflake = "DISGORD_TEST_GUILD_DEFAULT_EMOJI_SNOWFLAKE"

DisgordTestGuildDefaultEmojiSnowflake the default guild should have one custom emoji which can be retrieved during testing // eg: 486891339078696971

const DisgordTestLive = "DISGORD_TEST_LIVE"

DisgordTestLive set to true to properly test the functionality against Discord before a release is drafted

const GitHubURL = "https://github.com/LaevusDexter/disgord"

GitHubURL repository url

const JSONEncoding = "json"

JSONEncoding the json encoding identifier

const LockedMethods = false

LockedMethods signifies if the methods of discord objects should handle locking. I don't enjoy introducing this, but at the same time, I don't want to completely remove a easy way to activate locking for people that require parallel handling of objects.

Yes. They could set mutexes themselves, but if they want performance, they want to only lock when they actually deal read and write to the objects, not while doing casting, error checks, and other time consuming operations which often takes place in internal methods before actually interaction with the "unsafe" content.

TODO: reconsider - This option affects the behaviour in a breaking way.

const Name = "Disgord"

const UserAgent = "DiscordBot (" + GitHubURL + ", " + Version + ") " // "DiscordBot (%s, %s) %s"

const Version = "v0.16.5"