Whitelist frontend config values in description.exs
Lately I've been thinking about the AdminAPI, and the wild goose chase of adding BE config values into /api/v1/instance
(eg #1954 (closed))
I've been brainstorming better ways, and one idea is to whitelist values in description.exs. Eg:
This way an endpoint could do essentially the same logic as GET /api/pleroma/admin/config
except it filters only exposed_in_api
values and skips the OAuth check.
It could still be returned in /api/v1/instance
, maybe under ["pleroma", "config"]
.