Skip to content

Conversation

@iamdustan
Copy link
Owner

I took the tests modified from #17 but modified for a flattened API.

After experimenting with the firmata API directly I’m fairly convinced that exposing servoConfig as a property in any capacity would be a weak DX. Additionally, from looking at other libraries built on top of firmata they often introduced other concepts.

min/max may not be the best terms for this and I still don’t have a really solid grasp on how the min/max and writing a value interact (I think the servo I’m testing with needs to be calibrated or I just need to learn more about how hardware and electronics work).

The initial Servo implementation is pretty barebones as well. In due time we may very well want to introduce transition timing properties to it.

value: number;
}

class Switch extends Component {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be Servo, right?

@edvinerikson
Copy link
Contributor

Should probably export the Servo component in src/componnets/index.js too.

@iamdustan
Copy link
Owner Author

I knew I was much too tired while working on this. Thank you for the keen eyes, @edvinerikson.

@iamdustan iamdustan mentioned this pull request Jun 16, 2016
41 tasks
@iamdustan iamdustan force-pushed the servos branch 2 times, most recently from c6d9f93 to a957c47 Compare February 21, 2017 15:28
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

Successfully merging this pull request may close these issues.

3 participants