Currently, there is a bug that prevents deep-nested config fields from being validated. This is down to the way I was reading the config files and adding their values to the ValidationRepository. If a field was nested more than 2 times, only the first field at that level would be added to the repository.
For example, say we have this short-url config field:
Currently, there is a bug that prevents deep-nested config fields from being validated. This is down to the way I was reading the config files and adding their values to the
ValidationRepository
. If a field was nested more than 2 times, only the first field at that level would be added to the repository.For example, say we have this
short-url
config field:In this instance, the
ValidationRepository
would only load the following values:short-url.prefix
short-url.tracking.fields.ip_address
short-url.tracking.fields.operating_system
's value would not be loaded. This means the field couldn't be validated as expected.