Inaccurate models' data types

36 views
Skip to first unread message

Shane Jarrell

unread,
Oct 17, 2017, 10:46:50 AM10/17/17
to Developer Group for QPP APIs
Hopefully I'm not being too nit-picky here, but it appears that the model examples are not completely accurate. They express integer values when in fact they are decimals or floats (See Submission Score model below). From a schema perspective I feel this is misleading and confusing as the values returned can be decimals and are NOT truly integers.

Also, would it be possible to get an idea of the max length of messages that could be returned? Thanks so much! Appreciate all that you all do!

inline_model_24 {
data (ReturnedSubmissionScore, optional)
}
ReturnedSubmissionScore {
score (inline_model_7, optional)
}
inline_model_7 {
name (string, optional),
title (string, optional),
value (integer, optional),
detail (string, optional),
parts (Array[ScorePart], optional)
}
ScorePart {
name (string, optional),
title (string, optional),
value (integer, optional),
detail (string, optional),
original (inline_model_6, optional)
}
inline_model_6 {
name (string, optional),
title (string, optional),
value (integer, optional),
parts (Array[Inline Model 1], optional)
}
Inline Model 1 {
name (string, optional),
value (integer, optional)
}

Mari Miyachi

unread,
Oct 20, 2017, 7:27:28 PM10/20/17
to Developer Group for QPP APIs
Hi Shane! Good catch - we will fix this on our end!
Reply all
Reply to author
Forward
0 new messages