Amir Mofasser

Hi @jtyr I posted an alternative solution in #45 which doesn’t break compatibility which is important. Let me know what you think.

Although your contribution solves the problem, unfortunately it breaks compatibility since the API has changed requiring different inputs in the form of pointers. To get around this, each struct (in...

Yes, you are right, my proposal fixes the nullified fields problem but doesn't allow for updating fields selectively. I'm trying out another approach where types have accessor methods in order...

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 it...

> It's not required to update all types in config.go as only those that are editable should use pointers. I'm planning on implementing the same approach for all types. Which...

Internal functions are not exposed to users for this reason. As I said, the helper functions are very trivial. A function that returns a pointer to an argument will not...

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. I don't want to include...

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?

I’d rather avoid bloat the codebase than, providing convenience which in this case I argue that these functions do not. In any case I’m sure there are several libraries providing...

You are free to use whatever library you want alongside Huego. I took the liberation to create a library for your convenience: https://github.com/amimof/ptr