Organize CLICS API related utilities #1046
Labels
CI - Continuous Improvement
Continuously improve pc2 code quality, features and testing
Developer Issue
An issue which affects PC2 Developers but doesn't directly affect users.
Is your feature request related to a problem?
This feature is related to a minor code reorganization. Specifically, there is currently a routine to check the validity of a CLICS ID property. In addition, there's routine to change a (possibly) non-compliant name into a CLICS ID. These routines are used in the
ContestSnakeYAMLLoader
. It is proposed to move these routines to a CLICS specific utility class rather than have them inStringUtililities
....
Feature Description:
This feature request stems from this comment:
#1040 (comment)
...
Have you considered other ways to accomplish the same thing?
...
Do you have any specific suggestions for how your feature would be implemented in PC^2?
Each CLICS API package, 202003, 202306, has a "JSONUtilities" class. It seems like this is a good place for such routines. The ContestSnakeYAMLLoader is only going to be used to load "the latest" CLICS complaint CDP's, so, including the 202306 version of JSONUtilities, and moving the routines in question to that modules makes some sense.
...
Additional context:
#1040 (comment)
...
The text was updated successfully, but these errors were encountered: