Team2122/LeviTator

Resolve naming confusion around component Config classes

Closed this issue · 1 comments

At our meeting today an interesting point was brought up about confusion around what the Config suffix implies for component config object representations. At some point in the future, we should determine the optimal name for these classes to resolve any confusions about their purpose and contents.

I think Config doesn't necessarily refer to an external text file config, if that's where the confusion is. Configuration is configuration, no matter where it comes from.

If we are thinking about not using external text files, I would think that the best way store config for now would be to add field initializers in the Config classes.