I've been tasked with researching and making suggestions about refactoring/cleaning up some existing code in our code base. Presently, many of our projects depend on a Constants class, which contains all of the constants used in the library. While on one hand I get this choice - this object has a clear, defined purpose that's unique - I feel like it couples the code together too tightly.
For example, I have a library
ImportXmlClasses. Within that library, there is the
Constants class. In many cases, things that depend on
ImportXmlClasses wind up knowing about this
Constants class, and other Library's
Constants class as well.
Should I suggest this class be removed?