Client

Open Stories and Issues

I should be able to create and download a text file: Needed for the Arisia Use Case, for the interim before we have a proper export API. We should be able to press a button and download the current jobs data.
If I don't have JavaScript, I should see the "raw" version of the target page: Observed by one of Eric's users: if you have JS turned off, you currently get a blank page. Can we do something about that?
In the Client, DataSetting.setThing() is deeply suspicious: It's side-effecty; worse, InputGadget.thingId usually relies on it. It's a nasty code smell, and I've already encountered serious bugs caused by it. We should instead be rigorously setting data-thing explicitly when needed.
It looks like the Querki Client is leaking memory?: This is still anecdotal, but I'm seeing some Querki windows whose memory consumption is unreasonable. There is likely some leakage going on.
Restructure the Client to make use of modern JS modules: This is partly a research story, and is big, but it's potentially a big win
The Sharing Page should say what each Role means: Currently, the selection of Roles, during invitation, is a bit opaque.

Closed Stories and Issues

I can't recover from a Model Loop: If I manage to create a Model Loop -- a circular dependency -- there is no way to recover, because things crash too early.
If I try to look at a Space I can't read, I hang on "Loading...": Encountered by Roza -- part one of a two-part bug, I believe.