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

Tabs height and width defined as strings (version 2.1) #8

Closed
jfcote87 opened this issue Jul 20, 2019 · 3 comments
Closed

Tabs height and width defined as strings (version 2.1) #8

jfcote87 opened this issue Jul 20, 2019 · 3 comments

Comments

@jfcote87
Copy link

jfcote87 commented Jul 20, 2019

The height and width attributes of the tabs are defined as strings in the v2.1. Version 2 defined them as int32. API responses return numeric representation, not strings and samples in the swagger file also show the fields as integers.

@jfcote87 jfcote87 changed the title Tabs height and width defined as strings Tabs height and width defined as strings (version 2.1) Jul 26, 2019
@LarryKlugerDS
Copy link

Thank you for the bug report. I've reported this to the core team as EC-1615

@joeypeng
Copy link

joeypeng commented Aug 5, 2019

Hey @jfcote87 : As part of the v2.1 API we purposefully transitioned parameters to Strings until we properly implement and deliver on strong typing. The v2.1 response currently has STRING returned if you specified tab height/width. Where are you sing the response being returned as INT? And when you say "samples" showing INT, can you point me to where exactly that is? thanks!

@LarryKlugerDS
Copy link

Summary: this change is a planned breaking change for the v2.1 REST API.

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

No branches or pull requests

3 participants