State Management and Persistence Issues Across Various Modules #744

New Issue

kami_gawa · 2024-05-17T19:42:35Z

kami_gawa commented

2024-05-17 19:42:35 +00:00

Related to this, I've discovered numerous areas within the app where the data displayed is inconsistent or incorrect.

Beyond issues with pins/bookmarks and note-related data, another example of a problematic area is settings/moderation. Here, muted words are only displayed if they are stored in the state. This means that if you add a muted word and then refresh the page, the word no longer appears.

Is there a specific reason for this implementation approach, where sometimes state (like useLogin with various lists) is used, and other times data is fetched from an API without updating the state?

Please let me know if I'm missing something; otherwise, I believe this requires a significant refactor.

Also please can you grant me access to push to dev branches and open PRs?

Related to [this](https://git.v0l.io/Kieran/snort/issues/743), I've discovered numerous areas within the app where the data displayed is inconsistent or incorrect. Beyond issues with pins/bookmarks and note-related data, another example of a problematic area is settings/moderation. Here, muted words are only displayed if they are stored in the state. This means that if you add a muted word and then refresh the page, the word no longer appears. Is there a specific reason for this implementation approach, where sometimes state (like useLogin with various lists) is used, and other times data is fetched from an API without updating the state? Please let me know if I'm missing something; otherwise, I believe this requires a significant refactor. Also please can you grant me access to push to dev branches and open PRs?

kami_gawa commented

2024-05-17 19:44:56 +00:00

No description provided.

Screenshot 2024-05-17 at 21.44.32.jpg

432 KiB

kami_gawa changed title from ~~Application states are out of sync with BE data~~ to State Management and Persistence Issues Across Various Modules

2024-05-17 19:49:31 +00:00

Sign in to join this conversation.