title: Parse.User.current() not giving back a user object
body: <p>I am using Parse.com JS API. when using <a href="https://www.parse.com/docs/js/symbols/Parse.User.html#.current" rel="nofollow noreferrer">parse.user</a> method</p>
  
  <pre><code>getCurrentUser: function getCurrentUser(callback)
          {
              var currentUser = Parse.User.current();
              callback(currentUser);
          }
  </code></pre>
  
  <p>That would give my back:</p>
  
  <p><img src="https://i.stack.imgur.com/0bTbl.png" alt="result of the code 1"></p>
  
  <p>So since I am really interested in the attributes of this object I need to do something like this:</p>
  
  <pre><code>getCurrentUser: function getCurrentUser(callback)
          {
              var currentUser = Parse.User.current();
              //Not quite sure why I need to do that but I fugre out I cannot not really get the user object without
              var userObject = new Object();
  
              userObject.nick =  currentUser.attributes.nick;
              userObject.gender =  currentUser.attributes.gender;
              userObject.favoriteGenre = currentUser.favoriteGenre;
  
              callback(userObject);
          }
  </code></pre>
  
  <p>Which seems to me a bit dirty way of doing it?</p>
  
  <p>Is there a better way to overcome this obstacle? </p>
  
  <p>Note that I am using the method Parse.User.current(); so I can save a call to parse.com and get the info from the local storage.</p>
  
  <p>Thanks in advance!</p>
  
  <p><strong>EDIT:</strong></p>
  
  <p>I just saw I can use also:</p>
  
  <pre><code>Parse.User.current().get("nick");
  </code></pre>
  
  <p>Which seems cleaner, just make me think if I'll be in some case consuming my parse.com calls more than I want. Someone knows about that?</p>