Move from const enums about discord-api-types HOT 4 CLOSED

I've also had this issue. NextJS uses the isolatedModules compiler option which doesn't allow const enums, causing our dashboard to have magical numbers thrown around when doing things like filtering and displaying channels, each one requiring comments explaining what its representing. It also prevents dynamic lists using ts-enum-util for something like an option type dropdown, or using enums for validation with @IsEnum from class-validator

For now I've just stuck with copy/pasting enums without const for validation and some dynamic lists or not using them at all for filtering and other static use cases with isolatedModules enabled, but it would be really nice if it just wasn't an issue to begin with.

from discord-api-types.

Would be great to do this for sure especially now that discordjs/discord.js#7270 is done

from discord-api-types.

What's the use case for this? Getting the PascalCase names? The reason these enums are const and will most likely stay that way is to inline their values in the compiled code when using TS 👀

from discord-api-types.

I need to convert a string type such as INTEGER to it's type number so I can send that off to the discord api @vladfrangu
the commands are dynamically imported and processed at runtime so it can't be done at compile time

I wonder how discord.js does it for non typescript users providing INTEGER (how it resolves that to it's type number to send to the api

from discord-api-types.