improve component lib portion #124

Closed
tj opened this Issue Nov 4, 2012 · 10 comments

Comments

Projects
None yet
7 participants
Contributor

tj commented Nov 4, 2012

some things like building stand-alone versions should be more lib-ish, aka component.standalone() etc, and less logic in the executables

@tj tj referenced this issue Nov 12, 2012

Closed

programable api #162

Contributor

wilmoore commented Dec 24, 2012

👍

Contributor

ForbesLindesay commented Jan 1, 2013

This needs to also be an Asynchronous API

Contributor

tj commented Jan 1, 2013

yup definitely

Pickachu commented Feb 7, 2013

👍 for Asynchronous API

Contributor

ForbesLindesay commented Feb 8, 2013

It probably needs to be a duplicated API in the same style as node.js's fs APIs. For most things that can be serial they'll probably be faster in serial, but that may not be acceptable in examples like the component website.

👍 would really love to see a component-install API.

Contributor

micky2be commented Aug 9, 2013

👍 for an API

Contributor

jonathanong commented Dec 17, 2013

this is such a vague issue. can you guys add suggestions here? https://github.com/component/spec

Contributor

ForbesLindesay commented Dec 17, 2013

@jonathanong allow me to elaborate: The command line portions of this library (e.g. https://github.com/component/component/blob/master/bin/component-install) should only be concerned with passing options, getting the current working directory and writing log messages. They should then just pass that directly to an asynchronous method that is part of a public JavaScript API. This would make it easier to automate tasks with component.

Contributor

jonathanong commented Dec 17, 2013

i agree, but issues should be more specific. i.e. what API do you want? what's your use-case? we also should figure out specs first before we refactor.

@jonathanong jonathanong removed this from the 1.0.0 milestone Mar 29, 2014

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