Save State Always Dirty / Unsaved

[sour anvil]

Hi. On every single collection I have the save state is always "unsaved". As soon as I hit the save button, it activates again and I can't leave any page without it saying I have unsaved progress. This is accross all collections.

payload version 3.47.0

[fossil nimbus]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Lexical Migration - Migrating from Slate - Migration via SlateToLexicalFeature
• Relationship Field - How the data is saved - Querying and Filtering Polymorphic Relationships
• Drafts - Reverting to published

Community-Help:

• Build-time vs. run-time
• Replacing Payload Auth with a Custom Company Authentication
• payload cloud environments
• Deploying payload 3.0 with docker to Coolify

[pale rapids]

Do you have custom components that you're loading into the edit view that could cause the save state to change?

[sour anvil]

yeah i actually just figured it out!

i was using React.useState unecssarily in the component

getting rid of it and only using
const { value, setValue } = useField({ path })

fixed the issue

For clarification: I had a custom component with a map that sets a location value on most of my collections (heavily location based app). My React brain instantly tossed a useState in to handle the visual updating of the component. I was doing things like useEffect on the state object and then updating the form value inside it... instead of just updating the form value directly and using it to fill the component.