Removing Dynamic configuration #119
Comments
|
In d2d94fc I investigated using an automated tool to generate statically typed classes for config files. While useful it did not provide the desired level of flexibility. I think I'm going to go with the more boring option: Extending IAnalyzer with a series of statically typed (hand coded) classes/interfaces. |
|
The commit 864f7a4 had to deal with the forced removal of the custom built dynamic YAML DLL we had built. This issue is now a priority. |
atruskie
added a commit
that referenced
this issue
Feb 14, 2018
This commit is the bulk of the work required to remove DynamicYaml configuration and replace it with an extendable generic config file, which can also be used for static typing. Note, build fails, tests fail. More work needed. Note, nuget also needed to a package reinstall. It looks like the stylecop analyzers might be broken. By Adding a `Parse` method to the `IAnalyser2` interface we can allow for analyzers to parse their own config files to static classes 😀. However, this means the way we resolve Analyses by identifiers has changed and is now dependent on either an explicit argument, or the first two sections (separated by a period) of a config file name. This work was done for #119
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using
Dynamicfor configuration was useful but we are of course running into scalability problems as all sorts of weird technicalities that surroundDynamic.We want to replace our
Dynamicconfiguration implementation with static configuration classes.Investigate if we can do this automatically, or whether we just need to slowly move over.
The text was updated successfully, but these errors were encountered: