Dont display fields that are not readable in the right edge

In this screenshot, the password-hash field is actually not readable to the user, however the right edge is leaking the existence of this field (although there is no value displayed in it, and it is not editable). We need to hide fields that are not readable in the right edge.

[ef4]

Ideally, we shouldn’t leak the existence of non-readable fields to the client at all. So there would be nothing to ask about. So no, I’d prefer not to make readability something clients can even ask about in the authorization API.

They’re currently leaking because we don’t take permissions into account when we generate the code for the ember data models. There will be ember data attrs for all fields, even ones that aren’t readable. Doing this correctly involves running codegen later, and more dynamically.

If we need a quick solution, we can use the existing API for interrogating the schema. /api/content-types/YOUR_TYPE has a fields relationship, anything you can’t see in there isn’t something that we should render in the sidebar.

Eventually, the codegen step can happen as part of the cardstack data service when it goes to load cards. I can imagine that the spaces API request can come back with enough schema information that the client can dynamically generate the ember data models it will need to represent the cards as models.

[balinterdi]

@ef4 Ah, I totally overlooked that, thank you.

So the implementation should be extending what we currently have in the /permissions response by a readable-fields attribute that lists all the readable fields (just like we currently do for writable-fields). If a field is not in readable-fields we shouldn’t even render it.