Determine how to only import Kitura in the sample code instead of importing the individual modules about kitura

[dfirsht]

Comment by rfdickerson
Monday Jan 18, 2016 at 14:49 GMT

---

I thought our design is to modularize the entire Phoenix project into modules (like net, sys, io, etc). Should we instead have a single dependency target of Phoenix?

[dfirsht]

Comment by KALLNER
Monday Jan 18, 2016 at 15:28 GMT

---

In general I'm in favor of smaller modules, that way one doesn't always add quite so much bloat to one's application.

Some parts of Phoenix are optional and/or replaceable. Why have them embedded if one isn't using them?

[dfirsht]

Comment by babt
Monday Jan 18, 2016 at 15:36 GMT

---

I agree here with Shmuel. Small modules allow for leaner code. You only need to import what you're going to be using.

[dfirsht]

Comment by dfirsht
Monday Jan 18, 2016 at 16:47 GMT

---

The idea behind this issue is not to get rid of the individual modules, rather to have a peer of the modules called Phoenix that imports all of the other modules. This allows users who just want to use everything to only import one module. They will not need to know what the other modules are or what they contain.

[dfirsht]

Since we broke the project into different repos, this issue is no longer valid. The project is now purposefully separated so it should be explicit when we use functions across modules.