Create Endpoint to fetch and save Parse Dashboard settings in Database

[dblythy]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

As Parse Dashboard's features grow more and more, (in my opinion) it makes less and less sense to have every option configurable via startup parameters.

Feature / Enhancement Description

I am proposing storing the settings (such as columnPreferences, upcoming userPreferences) in the database. Features can then be modified on the fly via a Settings page on the Dashboard. This would then hopefully allow Dashboard users and permissions, column preferences, etc, to be changed on the fly. The only startup options would be appId, serverURL, etc, the rest would be configured via the Dashboard settings.

"Saveable" features:

• Dashboard Users (so you can create an manage permissions of dashboard users)
• Column Preferences
• Colors

Example Use Case

For the upcoming userPreferences feature (where you can specify access to Dashboard users), I think it makes sense to add a "Settings" page, with toggles for what each admin can access, along with a "create admin". I can't think of any way to do this through the dashboard without creating a server endpoint to save the settings in a database class.

Alternatives / Workarounds

Set via startup options.

3rd Party References

[mtrezza]

Thanks for suggesting! This definitely makes sense, just thinking about the column order and visibility which always resets in a new browser. Hasn't there been another issue in the past that discussed this feature?

[dblythy]

The column preferences already exists in the dashboard, it just has to be set via a startup option. I couldn't find any PR here that suggested saving it in the database

[mtrezza]

I am sure there is a recent conversation somewhere about this feature. Not sure whether on GH or in the forum. But it was only a discussion, not a PR.

[dblythy]

parse-community/parse-dashboard#1744

[mtrezza]

That's the one!