Skip to content
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

BUG: Unable to deserialize JSON to SecurityNamespaceDescription #47

Closed
tmeckel opened this issue Jan 10, 2020 · 4 comments
Closed

BUG: Unable to deserialize JSON to SecurityNamespaceDescription #47

tmeckel opened this issue Jan 10, 2020 · 4 comments
Labels
bug Something isn't working

Comments

@tmeckel
Copy link
Contributor

tmeckel commented Jan 10, 2020

Currently it's not possible to use the Security Namespaces - Query REST method, because the JSON deserializer isn't able to convert the received JSON structure into the corresponding GO struct SecurityNamespaceDescription.

An error is issued that the received SeparatorValue value can't be deserialized into an int32 (rune)

image

SeparatorValue *rune `json:"separatorValue,omitempty"`

According to the REST documentation the datatype for the separatorValue field is string and not rune (alias for int32).

image

@tmeckel
Copy link
Contributor Author

tmeckel commented Mar 14, 2020

@tedchamb Would you be able to fix this bug in a timely manner, as my pull request to the Azure DevOps provider for management of security settings cannot be merged until this bug is fixed here!

microsoft/terraform-provider-azuredevops#238

@tiwood
Copy link

tiwood commented Apr 6, 2020

@tedchamb, friendly reminder.

We have a few pull requests ready, which require this "bug" fixed.

@tedchamb
Copy link
Member

@tmeckel, thanks for filing this issue, and thanks for your patience with the slow turn around on the fix. The issue has been fixed by PR #64, and is available in the following release:

https://github.com/microsoft/azure-devops-go-api/releases/tag/azuredevops%2Fv5.1.0-b1

@tmeckel
Copy link
Contributor Author

tmeckel commented May 17, 2020

@tedchamb Awesome!! Many thanks having this nasty bug finally fixed!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants