Given the current structure of answers.conf, there's high chance of namespace(where namespaces are nothing but app names) collisions in nested Nulecule apps. For example, if there's a nested Nulecule application as below:
The params loaded for app2 in the different Nulecule applications will conflict each other in the section app2 of answers.conf. This is because the current namespace does not have any notion of hierarchy.
Solution
This can be easily solved in we update the way how we generate section names in answers.conf file to be more explicit as to which component in the Nulecule tree it is for:
[general]
foo=bar
[app1]
key1=var1
[app2]
key1=var2
[app3] # equivalent to general section for app3
key1=blah
[app3:app2] # component app2 for app3
key2=var3
[app3:app4]
some-key=some-val
Problem
Given the current structure of
answers.conf
, there's high chance of namespace(where namespaces are nothing but app names) collisions in nested Nulecule apps. For example, if there's a nested Nulecule application as below:The params loaded for
app2
in the different Nulecule applications will conflict each other in the sectionapp2
ofanswers.conf
. This is because the current namespace does not have any notion of hierarchy.Solution
This can be easily solved in we update the way how we generate section names in
answers.conf
file to be more explicit as to which component in the Nulecule tree it is for: