When you pass null into the team dropbox client AsMember method does it just use the current user?
dropboxTeamClient.AsMember(null) <- what account gets used?
There isn't a "current" user, so no user will be set. So, if you set null, it will just cause any user calls to fail.
Let me correct my question, if you are using an admin account and pass in null as a memberId, an error will occur.
If you are using a personal account, and use the team dropbox client and pass in null as the memberId for AsMember, it will ignore the null and use the current personal dropbox account?
Is that correct Gregory?
I don't know off hand what the behavior in that case would be, but if you're using a personal account, you shouldn't use a team client to begin with.
Currently it seems the default behavior is to use the personal account information.
I was considering using just the team dropbox client and passing it a memberId that is either a value of a team member or null if I am using a personal account, that way I do not have to bother with switching between both team client and dropbox client.
If the dropbox team client can be used as a regular dropbox client if passed null, what are the drawbacks of just using this to reduce similar code for admins and personal accounts?
I'm not sure there are any drawbacks, but that's not really the intended way of using it, so I wouldn't recommend doing so.