On Tue, May 26, 2015 at 03:20:22AM +0300, Nikita Karetnikov wrote: > > I believe these are the top things we could do to realize an API. > > They all feed into each other, too, so no task is too small. Plus, > > we would need to do most of this anyway if we are to start peeling > > things off into separate packages. > > I believe the scope of the mentioned things is too broad. In my > opinion, these are nice to have kind of things rather than top > priority. I'd suggest to focus. What is the problem that you're > trying to solve? Making the API, right? Which of the mentioned > things stop that from happening?
Nikita is right: one should do as little refactoring as necessary to fulfill a certain task. I still think the things I listed are important for one reason or another, but make of that what you will. > ... > > > * clean up types (remove IO, Handler, and Entity from top-level > > types, whenever possible) > > I'd start from here because it's already a problem. For instance, > DB cannot be used in some parts of the testsuite. It's essential > for the API for the same reason. After you change the types, > they'll indicate what needs to be changed to build the project. A > small change that makes a huge impact: a good first step. I'm happy to make this a priority for anyone interested in refactoring.
signature.asc
Description: Digital signature
_______________________________________________ Dev mailing list [email protected] http://lists.snowdrift.coop/mailman/listinfo/dev
