Closed bariscck closed 4 years ago
Added Friendship
response for follow
, unfollow
requests instead of Status
response.
Counters on User
is part of handler.users.user
request; If send request with primaryKey
counter values returns. I'm using it in my app.
I tested new User-Agents
in different devices, networks and I've also tested with your repo Swiftagram
it works for any request with LoginWebView
.
I didn't tested without LoginWebView
.
Replying here so it's easier to follow.
I'm perfectly aware User
-like instances when called directly return counters (for instance in /users/:id/info), but they don't in most other cases, e.g. followers, media users, tags, etc. I was just stating that's the reason why they were never included: they are optional fields, definitely not required in the endpoint response schema.\
But I agree with adding them, definitely not a problem 💪
About the user agent, there's no point in even storing it then since it's written in Device
but never read, as requests fallback to the default one.\
No point in keeping it in Device
, then. I suggest marking it unavailable or removing it entirely.
Just the better understand; should I remove the parts related to device
or User-Agent
?
Just the definition of userAgent
from Device
: it's never read now, so it serves no purpose. 😊
Just the definition of
userAgent
fromDevice
: it's never read now, so it serves no purpose. 😊
😊 Its removed.
Great 💪 I'll deal with linting (there are some trailing whitespaces, so it might fail in Travis, but no worries), merging this and bumping the pod version, np.
Do you know why the CI report is not showing up here? 😢 @TheM4hd1
@sbertix no idea what happened, it shows on travis panel, but not sure why it disabled here.
New
User-Agent
's fixedGoogle Play
header and LoginWebView related issues like #173 Added some missing properties toUserResponse
like follow counts, profile context vs.. AddedHighlighted Stories
request