pavlospt09/18/2018, 9:10 AM
. I have tried changing almost every regex in the config and still get specific issues reported, which is wrong. That leads me to think that custom values are not picked up. I am worried that I might have broken something when added
in the sense of a
picking up custom values and instantiating those Regexes instantly, but later on these fields being mutated and essentially nullified, leading to
picking up the default value when it’s time to execute for the first time. I am not sure if my thoughts are towards the correct direction, but it seems urgent enough to resolve this before going for v1.0.0.
mauin09/18/2018, 9:14 AM
flag as it will print the whole config that is going to be used in a parsed form. That should allow us to verify if the problem lies somewhere in parsing the config or if the config is correct but something is using it incorrectly. Thanks for looking into this @pavlospt!
pavlospt09/18/2018, 9:16 AM
mauin09/18/2018, 9:21 AM
pavlospt09/18/2018, 11:07 AM
mauin09/18/2018, 11:11 AM
mickele09/18/2018, 2:41 PM
skennedy09/18/2018, 5:35 PM
prints out the correct config for me, but it’s not respecting it