Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ConfigGenerator: generate module parent node dynamically instead of hardcoding #47

Open
Luolc opened this issue Jul 3, 2017 · 0 comments

Comments

@Luolc
Copy link
Contributor

Luolc commented Jul 3, 2017

Taken from #43 (comment)

The TreeWalker node is hardcoding currently. We should generate these nodes dynamically. For each module, we should get its parent module via its parent field, and then search the parent module in the module extract info map. If there is no such parent, then throw an exception and stop the process, otherwise generate every node we need dynamically in this way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant