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.

Sign up for GitHub

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

Jump to bottom

Remove hardcoded module and type names #5

Open
alexeyr opened this issue Oct 5, 2015 · 2 comments
Open

Remove hardcoded module and type names #5

alexeyr opened this issue Oct 5, 2015 · 2 comments
Assignees
@alexeyr

Comments

@alexeyr
Copy link

alexeyr commented Oct 5, 2015

See ScalanPluginConfig and maps in ScalanPluginState
@alexeyr alexeyr self-assigned this Oct 6, 2015
This was referenced Oct 12, 2015
Open
Open
@alexeyr
Copy link
Author

alexeyr commented Oct 12, 2015

@Module from #8 either has an argument for modules this module depends on, or they are discovered automatically (how? Maybe use specific dependencies in self-types?).

@alexeyr
Copy link
Author

alexeyr commented Oct 12, 2015

All modules can be collected as the first stage of plugin, their dependencies as the second (if needed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alexeyr alexeyr

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@alexeyr