Found in prod testing: switching to a locked account handed to you brought only its mail.
A new useSession.viewAccountFor(cap) gives the locked account in view when it offers that capability, and the reader's own otherwise.
The calendar, contacts and files stores use it for what they show, and are re-initialized when the account in view changes, just as mail is.
Files starts at the locked account's top level when you switch in or out.
Settings, signature images and push keep ownAccountFor. They live in the reader's own account, so nothing of the reader's is written into the locked one.
Needs inbuxa-server #68, so that a delegate can reach a kind of data the locked account has none of yet (such as empty Files) and add to it.
Tests: 1 new, 1471 pass. Checked in Chrome against a local server with #68: Calendar, Contacts and Files each showed the locked account under the red bar.
Found in prod testing: switching to a locked account handed to you brought only its mail.
- A new `useSession.viewAccountFor(cap)` gives the locked account in view when it offers that capability, and the reader's own otherwise.
- The calendar, contacts and files stores use it for what they show, and are re-initialized when the account in view changes, just as mail is.
- Files starts at the locked account's top level when you switch in or out.
- Settings, signature images and push keep `ownAccountFor`. They live in the reader's own account, so nothing of the reader's is written into the locked one.
Needs inbuxa-server #68, so that a delegate can reach a kind of data the locked account has none of yet (such as empty Files) and add to it.
Tests: 1 new, 1471 pass. Checked in Chrome against a local server with #68: Calendar, Contacts and Files each showed the locked account under the red bar.
Switching to a locked account handed to the reader moved only the mail.
Now calendar, contacts and files follow it as well, through a new
viewAccountFor that the three stores use for what they show. Settings,
signatures and push keep ownAccountFor, so nothing of the reader's is
ever written into the locked account (inbuxa AL-7).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found in prod testing: switching to a locked account handed to you brought only its mail.
useSession.viewAccountFor(cap)gives the locked account in view when it offers that capability, and the reader's own otherwise.ownAccountFor. They live in the reader's own account, so nothing of the reader's is written into the locked one.Needs inbuxa-server #68, so that a delegate can reach a kind of data the locked account has none of yet (such as empty Files) and add to it.
Tests: 1 new, 1471 pass. Checked in Chrome against a local server with #68: Calendar, Contacts and Files each showed the locked account under the red bar.