You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably related to #45 -- the recycle parameter is marked as bool without any omit directive. It works for creating the scene but not for updating it.
Steps to reproduce the issue:
Try to update a scene name
Error: parameter, recycle, is not modifiable
Describe the results you received:
I am implementing a terraform provider, this is the JSON: {"name":"Testing","recycle":false}
│ Error: ERROR 8 [/scenes/jeU0J-6kXNVvnnL/recycle]: "parameter, recycle, is not modifiable"
I am learning go as I write this provider, if you provide me some pointers I can contribute towards the solution.
My naive solution would be adding a map to the "update" instead of using the struct so we have fine control over the elements -- but I think the solution from #45 would solve this in a better way.
The text was updated successfully, but these errors were encountered:
@roperto Thanks for reporting. This behavior of the Huego API is a known issue and is brought up in #45. While working to fix that issue, the V2 API was released. I’m now currently working on releasing a V2 client with all these field pointer issues fixed.
I need developers testing out the new client. If you’re interested, I can notify you once I have something ready for testing.
Probably related to #45 -- the
recycle
parameter is marked asbool
without anyomit
directive. It works for creating the scene but not for updating it.Steps to reproduce the issue:
Describe the results you received:
I am implementing a terraform provider, this is the JSON:
{"name":"Testing","recycle":false}
│ Error: ERROR 8 [/scenes/jeU0J-6kXNVvnnL/recycle]: "parameter, recycle, is not modifiable"
Describe the results you expected:
Hue Bridge Version
Can I help?
I am learning go as I write this provider, if you provide me some pointers I can contribute towards the solution.
My naive solution would be adding a map to the "update" instead of using the struct so we have fine control over the elements -- but I think the solution from #45 would solve this in a better way.
The text was updated successfully, but these errors were encountered: