-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow both int and string in more places #219
base: master
Are you sure you want to change the base?
Conversation
088d2e4
to
935d100
Compare
Still need to fix
and maybe #220:
(althought that one doesn't block me quite as much) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work!
@mrwonko thanks so much for all this work! If you are happy to address those issues too, that would be fantastic. |
Will do, I just ran out of time on Friday. |
- Use Client of httptest Server - Set RetryTimeout in datadogClient so it doesn't retry indefinitely on error - Move testdata into the well-known testdata/ folder so test caching etc. works properly - Return error from mock Datadog server instead of calling t.Fatal, which is only allowed in the test's main Goroutine - Use reflect.DeepEqual to shorten Screenboard test
We'll use that type for other things besides precision.
Besides integer sizes in pixel (e.g. 768) the API can also return percentages (e.g. "100%"). Fixes zorkian#192
They happen.
This introduces a new type StrBoolD (similar to StrIntD) for types that can be either strings or bools in JSON. Fixes zorkian#220
eb15c0c
to
b04c74e
Compare
As far as I'm concerned this is now done, all the screenboards from my project work now. |
Thanks @mrwonko! I'll have some time to review and hopefully merge tomorrow. |
@masci as a Datadog employee with most likely more insight in your API, what is your opinion on this? While I very much appreciate the library working around quirks of the DD API, it is becoming so inconsistent. I'd hate to continue to introduce breaking changes each time people find them. Any ideas on a structural approach to this problem, @mrwonko, @masci. @nyanshak, @yfronto or @zorkian, care to think along? |
@ojongerius, @mrwonko What is the status update of this? would this fix https://github.com/terraform-providers/terraform-provider-datadog/issues/105? |
Hey @ojongerius From Datadog here. I've communicated internally to put these issues on the radar but don't have any timeframes for when a longer term fix would be possible unfortunately. I'm in favor of pushing this forward if you are, to resolve the existing issues people are facing. |
Is this PR still likely to get merged? Just ran into the |
@ojongerius Also wondering what the status on this one is as it seems to have been dormant for >9 months now? Ran into the problem today as I'm no longer able to update a screenboard with container tiles using the terraform provider due to the error |
It seems everybody is in favor, I am not sure to understand why this is not merged @ojongerius |
This is basically a combination of the apparently abandoned #198 and #195 with some additional cleanup and added tests. The goal is fixing #192.
With the fixes in place I noticed additional type mismatches for
Params.Count
,Params.Start
andConditionalFormat.Value
, which I fixed in the same way.