We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Some fields are defined as 'Integer', e.g.:
c_nonce_expires_in: OPTIONAL. Integer denoting the lifetime in seconds of the c_nonce.
c_nonce_expires_in
c_nonce
I'm not sure what this really means (is it invalid to send 60.0?) and what it's implications for interoperability/conformance testing are.
60.0
I'd suggest changing to 'number'.
The text was updated successfully, but these errors were encountered:
is this somewhat related to issue #90?
Sorry, something went wrong.
@Sakurann probably not directly. That one is about dates, this one is about time intervals.
(This one is trivial, it could probably be considered editorial. I might even do a PR for it...)
Change 'Integer' to 'Number'
dd62e9c
As this is just in a JSON response restricting it to integer doesn't really make any sense, it's can just be a number. closes #100
jogu
Successfully merging a pull request may close this issue.
Some fields are defined as 'Integer', e.g.:
I'm not sure what this really means (is it invalid to send
60.0
?) and what it's implications for interoperability/conformance testing are.I'd suggest changing to 'number'.
The text was updated successfully, but these errors were encountered: