Several headers of PhASAR #include nlohmann/json which requires consumers of phasar to integrate nlohmann/json into their codebases as well. This is not only inconvenient for users, it also ties us to nlohmann without an easy way of switching JSON libraries under the hood.
To fix this, we introduce an intermediate layer (for now just for the TaintConfig) that represents the same json data but hides the implementation details
Several headers of PhASAR #include nlohmann/json which requires consumers of phasar to integrate nlohmann/json into their codebases as well. This is not only inconvenient for users, it also ties us to nlohmann without an easy way of switching JSON libraries under the hood.
To fix this, we introduce an intermediate layer (for now just for the TaintConfig) that represents the same json data but hides the implementation details