Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
pleroma-meta
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards
  • Pleroma
  • pleroma-meta
  • Issues
  • #34

Closed
Open
Opened Apr 01, 2020 by feld@feldMaintainer
  • Report abuse
  • New issue
Report abuse New issue

Design API for storing FE settings

What would an ideal API look like for storing FE settings in the database?

I'm thinking we want to achieve the following:

  • PATCH for partial updates. New FE settings would be lost when using older FE if every save replaced all data
  • JSON, keyed on software name so various FEs can utilize it and obtain consistency
  • subkeyed for profiles? This would allow the power users to create named profiles so they could keep their desired settings. Also allows you to easily switch to maybe a "public" mode where you add more keyword filters, enable NSFW cover, etc.

Would love to hear your thoughts @hj @shpuld

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: pleroma/pleroma-meta#34