Closed jesQM closed 4 years ago
Looks like the method which returns the username, instead, returns a Proxy object, rather than a string or another object which does have a toString (apparently proxys dont have)
static async getName(){
var session = await auth.currentSession();
var username = data[session.webId].vcard_fn;
return username;
}
However, the Home view, uses that same method in the same way and works... that is weird
Reduced the priority as a patch (not a very clean one) is now fixing this, it can still be improved.
I found this when trying to upload a route:
I have checked the commit in which it is caused by navigating until the error was not present: e78e3caf8ac70cfb7852e537d8a54c76e814c16e
Looks like, If I try to change the username provided to the JSON.stringify method, the exception is not caused.