Closed gr2m closed 8 years ago
@codyzu these 3 issues are all related to username change:
here is some background information on it: https://dl.dropboxusercontent.com/u/732913/hoodie/2016-04-21-username-change-code-background-info.mov
You can un-skip this test in hoodiehq/hoodie-account to make sure it all works together. To set it up locally, git clone the three repos, then run npm link
in the hoodie-account-server
and hoodie-account-client
folder, then run npm link @hoodie/account-server
and npm link
@hoodie/account-clientin the
hoodie-accountfolder. Now you can do changes in the server and the client, and immediately test it when restarting the server or the tests in
hoodie-server`
Let me know if you want to give this a try, or if you have any farther questions
@gr2m I'll start looking at the details today... I won't have any results until wednesday (when I have some hours reserved for this) :+1:
okay, wow, I guess that’s it :) The remaining issues can be done as part of the next release :)
follow up for https://github.com/gr2m/milestones/issues/87
Ready
hoodie.account.signOut()
must resolve with account properties, currently is undefinedPUT /session to return 401 Unauthorized error when user cannot be found
Implement PATCH /session/account route
Implement
hoodie.account.update(changedProperties)
implement
hoodie.account.destroy()
hoodie.account.fetch()
,.update()
,.profile.fetch()
and.profile.update()
should fail with UnauthenticatedError if session is invalid, but currently fails with "Not FoundError"Implement
hoodie.account.isUnauthenticated()
Implement
reauthenticate
eventReturn custom Conflict error
Return custom Not Found error
Implement
hoodie.store.isPersistent()
Reset
hoodie.store
correctly onsignout
eventReset
hoodie.store
onsignin
eventpass options.hooks to signup / signin / signout events
trigger "update" event when account.update succeeds
renew session after changing username / password
call hoodie.store.connect() on page load if user is signed in
Implement username change
account.update
: set session ID fromx-set-session
response headerPATCH /session/account: respond with
x-set-session
headerStore Server: Proxy to PouchDB instance
rename
/hoodie/bundle.js
to/hoodie/client.js
rename
/www
folder to/public
simplify Internal Module Architecture
make the Hoodie fallback webapp more helpful
Tracker app: items are disappearing after I log out and log back in
Needs instructions
unify test setup
remove /session/account from spec
Inconsistencies between implementation and API spec
Discussion
how to add a .createdBy property automagically to all documents created with hoodie.store.add?
rename
bearer
in ourAuthorization
header tosession
, because that’s what it is, and we don’t use bearer tokens anywhere else in our code. It’s unnecessary confusing. So instead ofAuthorization: bearer sessionid123
header, we would haveAuthorization: session sessionid123