Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
why di config/loader parsed result is not compatible to neon format? #134
I am improved the config class with neon, now it can be write like this:
it can merge config in every env, I'd like it :-P
but when I try to use addConfig() method to set di config to compiler, it was error, because
could you make they to be same class? or compatible neon entity in Validator?
look, by the sample I can make di like this:
it's no problem.
now, I want to do something before config load, and I still use neon format. so I couldn't use
and will throw exception:
because neon::decode() will return entity object, di system need di\statement, although they look very similar. I think it should be more compatible.
var_dump for my parsed config:
you can see my config class in the links:
It is bind to neon libs, I can add some code to trans neon\entity to di\statement, but it is low efficiency.
I will try to add neon\entity support to di libs tomorrow.