I.e., a code for each error that may be thrown that can be included in the error output so users can better identify the source of the error
Consider how to incorporate library structure - i.e., where in the source code the file may come from - and the type of error - e.g., invalid arg data type, invalid HW config for whatever reason, ID not found, ID pool or RMgr maxed out, etc.
[ ] design doc first: prefixing, number coding, different levels (e.g., error vs warning)
[ ] create an error code dictionary in the library, either in its own file/class, or in Constants. Create a variable for each error code, named with the error code itself, and valued by a tuple: ("string error code, should match the name", "Error msg")
[ ] whenever throwing errors, use the code variable
May choose to use the Error.cs - expanding it in some form - in lieu of or in addition to the dictionary idea described above ^, or may delete this class altogether
I.e., a code for each error that may be thrown that can be included in the error output so users can better identify the source of the error
Consider how to incorporate library structure - i.e., where in the source code the file may come from - and the type of error - e.g., invalid arg data type, invalid HW config for whatever reason, ID not found, ID pool or RMgr maxed out, etc.
May choose to use the Error.cs - expanding it in some form - in lieu of or in addition to the dictionary idea described above ^, or may delete this class altogether