Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide provisions for 3PA's to persist settings/app data to the API #361

Open
asimons04 opened this issue Apr 25, 2024 · 3 comments
Open
Labels
enhancement New feature or request

Comments

@asimons04
Copy link

asimons04 commented Apr 25, 2024

Creating this from a thread in the chat.

Basically, there's no way to cover all the possible settings various third-party apps can have via distinct settings columns. Additionally, 3PAs may not currently or even want to poll the server for those and prefer to just have a place to sync their local settings for persistence or to access from another device.

Essentially, provide an authenticated endpoint a user can call that will accept a JSON POST containing the serialized app settings and a companion GET one to retrieve those.

Will leave the specific implementation details to the comments.

@jgrim jgrim added the enhancement New feature or request label Apr 25, 2024
@jgrim jgrim added this to the Version 0.1 - Parity milestone Apr 25, 2024
@jgrim
Copy link
Member

jgrim commented Apr 25, 2024

@Pdzly this will be part of the new Sublinks API.

@Pdzly
Copy link
Member

Pdzly commented Apr 25, 2024

I can already sketch it out in the new api #359

@jgrim
Copy link
Member

jgrim commented Apr 25, 2024

I can already sketch it out in the new api #359

Great!

@jgrim jgrim changed the title [Feature Idea] Provide provisions for 3PA's to persist settings/app data to the API Provide provisions for 3PA's to persist settings/app data to the API Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 🔖 Ready
Development

No branches or pull requests

3 participants