GIVEN Alex sees that EnderChest supports new functionality that's controlled via newly introduced keys set within the enderchest.cfg or shulkerbox.cfg files
THEN EnderChest will open, validate and rewrite all config files (or just the chest configuration / specified box config) in the latest format
SO that she's not going in blind trying to set the key values and leverage the new features
Notes
This could be done by default every time a config is read EnderChest reads in a file, and it could be done intelligently by checking against the version set in the properties tag
This could be done interactively if the user doesn't specify what should be reloaded
This could also check instances (but only if #54 is resolved first) and remotes, though this should not be done by default
GIVEN Alex sees that EnderChest supports new functionality that's controlled via newly introduced keys set within the
enderchest.cfgorshulkerbox.cfgfilesWHEN she runs the command
THEN EnderChest will open, validate and rewrite all config files (or just the chest configuration / specified box config) in the latest format
SO that she's not going in blind trying to set the key values and leverage the new features
Notes