You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Then when I run from app I expected that each subgenerator will have access to the value of its options, e.g., in sub-gen1 I may be able to read str2. But, the behavior I'm having here is that app subgenerator have all options values (even the ones defined in the other two subgenerators) and sub-gen1 and sub-gen2 are not able to read the value of its own options, like the output below:
Hi :)
I have a scenario here with 3 subgeneratos following the structure below:
The app subgenerator is composed by sub-gen1 and sub-gen2. Each one define its own options inside its constructor:
Then when I run from app I expected that each subgenerator will have access to the value of its options, e.g., in sub-gen1 I may be able to read
str2
. But, the behavior I'm having here is that app subgenerator have all options values (even the ones defined in the other two subgenerators) and sub-gen1 and sub-gen2 are not able to read the value of its own options, like the output below:Is this the expected behavior under the composability of generators? How can I propagate these values from
app
to the others subgenerators correctly?If needed, I have a dummy generator created to demonstrate this behavior: https://github.com/adautomendes/generator-dummy-adauto
The text was updated successfully, but these errors were encountered: