Accept body parameters for /api/pleroma/notification_settings #738
No reviewers
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#738
Loading…
Reference in a new issue
No description provided.
Delete branch "Oneric/akkoma:notif-setting-parameters"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This brings it in line with its documentation and akkoma-fe’s expectations. For backwards-compatibility URL parameters are also still
accept with lower priority. Unfortunately this means duplicating the parameters and description in the API spec.
Usually Plug already pre-merges parameters from different sources into the plain params parameter which also gets forwarded by Phoenix.
However OpenApiSpex 3.x prevents this albeit a change is planned for 4.x, see:
https://github.com/open-api-spex/open_api_spex/issues/334
https://github.com/open-api-spex/open_api_spex/issues/92
Fixes: #691
Fixes: #722
all seems good, thanks!