Document save options drop-down: remember previously selected

[abovedave]

Expected behavior

Per-user remember the previous state of this button - handy when bulk entering data.

Actual behavior

Always reverts to "save and continue"

[danwdart]

Should this be stored upon the user in the database, or should it only be localStorage?

[abovedave]

I think db so it persists across device and session?

[eduardoboucas]

Worth noting that currently Publish doesn't store any metadata in API, so this is something that we need to consider and plan for carefully.

[danwdart]

I think therefore that this is a synced PUT/GET to /${version}/${db}/users from the... redux store, maybe?

[eduardoboucas]

And who creates that users collection?

[danwdart]

The users would already be there, it's the same users as one logs in using, the auth?

[eduardoboucas]

We're getting rid of that authentication method in favour of ACL, remember? ☺️

[danwdart]

Of course, was a save place decided?

[eduardoboucas]

Likely this: dadi/api#453. Until then, this one is blocked. 🚫

[danwdart]

Okay - nice thanks

[eduardoboucas]

⏳ Waiting for API 4.2.

[eduardoboucas]

This can now be worked on, since API 4.2.0-rc4 (which the preview instance is running) includes support for arbitrary data against client records.

I propose a field for storing this preference, like publishSaveOptionsLastUsed (all fields should start with publish). This action allows you to save data against the client, so you should be able to use that.

If you have any questions, ping me on Slack.

[danwdart]

Has the location for getting client data back out changed at all?

[eduardoboucas]

Should all be here.

[danwdart]

cool thanks

[danwdart]

@eduardoboucas this custom field, should it go under "data" in the user?

[danwdart]

I figured it is "data" and made it work without any extra API changes.