1.2.0 Feature: Push Notifications: Local Device State

[QuintinWillison]

One of a family of pull requests addressing #3.

[qsdstefan]

The way I understood it, Local Device State is now a separate feature as part of the Push Notifications section? Approved.

[QuintinWillison]

Thanks for your comment, @qsdstefan. To address your question:

Local Device State is now a separate feature as part of the Push Notifications section?

The answer is either a light yes or a heavy no, depending on what perspective you look at this from...

The light Yes: From the perspective of someone viewing this with an existing understanding of our IDL and the API structures that it translates to in our SDKs, then "now a separate feature" - describing a move operation - sounds like the correct analysis.

However, this isn't a move. It represents what we already have, from a different angle of view...

The heavy No: From the perspective of the way we're representing our canonical features tree in this repository, I've intentionally deviated from the IDL structure when that is more logical in abstract. The intention is to represent our feature hierarchy in a way that is most logical from a user's perspective, flowing down from node to node. The contents of sdk.yaml is not an IDL or an API.

These feature nodes are intended to be referenced using their fully qualified path into the tree. So, in this case, that's:
Push Notifications: Local Device State

Hopefully an appropriate balance between human and machine readability. 🤞

It's why I implemented the CSS-powered tooltips as you scroll up and down the rendered output: