Currently when we get objects like guildConfig and economyUsers, we compare them with the 'default' object (in the types folder) so make sure they are up-to-date, since fields can be added between versions.
The current way this is done is problematic, as it only copies 1-layer deep and doesn't work for complex data types like nested objects, arrays, etc...
Currently when we get objects like
guildConfig
andeconomyUsers
, we compare them with the 'default' object (in the types folder) so make sure they are up-to-date, since fields can be added between versions.The current way this is done is problematic, as it only copies 1-layer deep and doesn't work for complex data types like nested objects, arrays, etc...