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

Improve changed state tracking ability in the RESPECT editor. #512

Open
szczz opened this issue Jan 16, 2025 · 0 comments
Open

Improve changed state tracking ability in the RESPECT editor. #512

szczz opened this issue Jan 16, 2025 · 0 comments
Labels
Enhancement New feature or request

Comments

@szczz
Copy link
Member

szczz commented Jan 16, 2025

Description

Discussed in the 01/14/2025 Platform meeting.

RESPECT does not have a reliable way of tracking whether changes have been made to a storyline product. For example, if you load a storyline, create a new slide, and then delete that slide, RESPECT will indicate that there are unsaved changes even though the product is in the exact same state as when it was loaded. This leads to issues and requires workaround for other systems as discussed in #459.

We should introduce proper state tracking, so that we can avoid future issues and workarounds.

Proposed solution

@yileifeng has proposed the following initial idea:

An initial idea is to store a separate copy of the last saved version of config slides and the metadata object inside a store upon loading in a product. Then, we could replace the current watcher behavior that updates the save status indicator with a deep object comparison method (e.g. Lodash).

Related Issues

#123

@szczz szczz added the Enhancement New feature or request label Jan 16, 2025
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
None yet
Development

No branches or pull requests

1 participant