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

Blog: Automatic save #336

Open
rajat1saxena opened this issue May 13, 2024 · 0 comments
Open

Blog: Automatic save #336

rajat1saxena opened this issue May 13, 2024 · 0 comments

Comments

@rajat1saxena
Copy link
Member

The blog posts should be automatically saved. All the new changes will be saved in a draft state and will be published, when the user pressed the Publish changes button.

Specs

Model

We will create a new property in Courses model which will store the draft state.

Logic

The frontend will save the data, every 3 seconds if there are updates. The calls should be debounced. On the backend, all the changes are saved to the new property (mentioned in Model section).

When the user presses Publish changes, we will move the data from draft state to the actual property.

@rajat1saxena rajat1saxena converted this from a draft issue May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

1 participant