The first version of the /raid_maps command uses an Enum class to represent all the given Raids that a user could request in a command. However, this enum also holds an attribute named directory which hardcodes the name of the directory which contains all the image and attachments to send through Discord chat. The same has been done for RaidEncounter. This task is to investigate if there is a better solution to hardcoding these file locations and instead use a configuration-based solution where each Raid enum instance has a property set in a .yaml file. This way, we can separate and de-couple the responsibility of having the file locations in the enum classes and instead externalize the locations to a configuration file.
The first version of the
/raid_mapscommand uses an Enum class to represent all the given Raids that a user could request in a command. However, this enum also holds an attribute nameddirectorywhich hardcodes the name of the directory which contains all the image and attachments to send through Discord chat. The same has been done for RaidEncounter. This task is to investigate if there is a better solution to hardcoding these file locations and instead use a configuration-based solution where each Raid enum instance has a property set in a.yamlfile. This way, we can separate and de-couple the responsibility of having the file locations in the enum classes and instead externalize the locations to a configuration file.