otto/value: support conversion to lowerCamel naming

[robfig]

I was interested in exposing Go struct properties and methods to JS code using the conventional casing, lowerCamel.

For example,

type Example struct {
    Name string
}

func (Example) Update(newName string) error {
    // ...
}

Right now this is converted to a JS object with Name and Update properties. One way to allow for customization is to update the value conversion logic to respect otto:"name" struct tags, but that would not help the method names. For that it would need some kind of out-of-band configuration on _runtime, which seems undesirable.

I think my only option right now is to copy the conversion code (runtime.toValue) into my project and then customize it freely.

Does that seem right, or do you have any ideas that I could contribute back?

Thank you!
Rob

[stevenh]

A vm creation option to control the ingest of fields and method names seems like the most appropriate option.

For fields you're correct using tags would allow for more customisation but not sure how useful that would be in practice given a top level vm option.

Thoughts?