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

Need to change sectionid from int to long in article results #262

Closed
zrilo opened this issue Jan 12, 2017 · 0 comments · Fixed by #264
Closed

Need to change sectionid from int to long in article results #262

zrilo opened this issue Jan 12, 2017 · 0 comments · Fixed by #264
Labels

Comments

@zrilo
Copy link

zrilo commented Jan 12, 2017

Bug: I have noticed that sectionids in zendesk are now longer that int32 and as such search results are getting a "JSON integer .... is too large or small for an Int32" parse error

Could you please update the sectionid in the below file to be a long instead of int
ZendeskApi_v2/src/ZendeskApi_v2/Models/Articles/Result.cs

You may need to update sectionid type in other parts of your model as well.

Thanks

@mozts2005 mozts2005 mentioned this issue Jan 26, 2017
mozts2005 added a commit that referenced this issue Jan 26, 2017
* Changed all public properties to from int to long per docs
https://developer.zendesk.com/rest_api/docs/core/introduction#id-integers

fixed #263, fixed #262

* updated version number

* fixing double build

* adding notification to build

* change notification
mozts2005 added a commit that referenced this issue Jan 26, 2017
* Changed all public properties to from int to long per docs
https://developer.zendesk.com/rest_api/docs/core/introduction#id-integers

fixed #263, fixed #262

* updated version number

* fixing double build

* adding notification to build

* change notification

* fix build number

* file clean up
mozts2005 added a commit that referenced this issue Mar 9, 2017
* Changed all public properties to from int to long per docs
https://developer.zendesk.com/rest_api/docs/core/introduction#id-integers

fixed #263, fixed #262

* updated version number

* fixing double build

* adding notification to build

* change notification

* fix build number

* file clean up

* Updating release notes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants