642980 - cleanup account objects

Status: RESOLVED WONTFIX

(Mozilla Labs :: F1, defect)

Description

[Shane Caraveo (:mixedpuppy)]

The account object contains unnecessary redundancy for historical reasons and needs to be cleaned up.  Here's a sample of what currently is created:

{
"username": "mozmotest", 
"profile": {
  "displayName": "Shane Carav\u0119o", 
  "providerName": "Twitter", 
  "photos": [{
     "type": "profile", 
     "value": "url to image"}], 
  "accounts": [{
     "username": "mytestaccount", 
     "domain": "twitter.com", 
     "userid": 1234567890}], 
  "published": "Thu Sep 02 19:53:53 +0000 2010", 
  "identifier": "http://twitter.com/?id=1234567890"}, 
"domain": "twitter.com", 
"oauth_token_secret": "My Super Secret OAuth Token", 
"userid": "1234567890", 
"updated": "2011-03-18T14:03:58.742713", 
"oauth_token": "My less than secret OAuth token", 
"key": "3e464104-51a3-11e0-9b46-d49a200eaa62"
}

Comment 1

[Philipp von Weitershausen [:philikon]]

Which fields would be removed? The schema might be of importance here for bug 	642656 and bug 642660.

Comment 2

[Shane Caraveo (:mixedpuppy)]

I would remove username,userid,domain from the top level of the object, and rely on the accounts in the profile.  key is also something that I think is unnecessary (holdover from the server side db).  And maybe updated can go.  The profile object could be used as a basis for other public api's (profile.get from openwebapps?).