The route GET /v1/profiles/{userId} which retrieves a user's profile from which we parse the interests for the "cloud text' doesn't return any specific weights for each interests.
Our solution was to expect the interests to be returned sorted in ascending order so that we can parse and assign text size based on the order in which they are returned.
footnote
commented
9 years ago
The route GET /v1/profiles/{userId} which retrieves a user's profile from which we parse the interests for the "cloud text' doesn't return any specific weights for each interests.
Our solution was to expect the interests to be returned sorted in ascending order so that we can parse and assign text size based on the order in which they are returned.