Jiri Tyr

We could create new type with pointers (e.g. `Copy` - old, and `CopyPtr` - new) and change the `UpdateConfig` method to accept an `interface{}` instead of `Config` and then if...

> I understand that it's convenient but those kind of helper functions are so trivial that they might as well be created by the user. In our case we use...

I have made the pointer methods internal. But as a user of this API implementation, I'm really not happy that you don't provide me with this functionality and that you...

> I'm not forcing you to do anything. You may use whatever library you want for this purpose. Or whatever Hue API implementation for that matter. By not exporting the...

> It’s literally 3 lines of code. You mean it’s too difficult for you so you need a library to do that for you? It's more about how convenient instead...

If there is such library then let's use it instead of adding those methods here. Please point me to such library and I will amend the PR accordingly.

What about https://github.com/AlekSi/pointer?

Good stuff. Let's shorten the names if it's already in the `ptr` package. I have created PR for that here: https://github.com/amimof/ptr/pull/1

This is the fundamental issue with this Golang implementation of of the Hue API. It doesn't allow to update only specific values - it always sending all fields of the...

@amimof Plese see PR https://github.com/amimof/huego/pull/49 for possible solution.