I have some
enums in a concrete API/library that will be publicly used by application projects. My problem here, is that I cannot write an interface to these
enums (that I know of). I should have thought of this before starting the project, but I did not. What really complicates this is that some of the methods accept/return the
enums as arguments/parameters.
Is there any way to keep my code loosely coupled, while still keeping the
enums publicly facing the application?
Would it be acceptable to just put the
enums into the
interface library (as opposed to the concrete's/implementation's library)?