New Item has changes even without any modifications

[joselcvarela]

Preflight Checklist

• I have completed all Troubleshooting Steps.
• I'm on the latest version of Directus.
• There's no other issue that already describes my problem.

Describe the Bug

When I am trying to leave the New Item view without any changes the confirmation modal appears.
Also, when I click Discard Changes it shows the confirmation modal again and this process repeats and I am not able to quit this view.

To Reproduce

I am not sure why this started happened now, but this is easy reproducible:

1. Create a collection
2. Open the New Item view on this collection
3. Try to leave. Confirm leave modal must appear.

Errors Shown

See this screenshot

Those are the edits, but I didn't make any change 🤔
The nextval thing comes from the default value from PostgreSQL

What version of Directus are you using?

9.4.3 (e258f3d - main)

What version of Node.js are you using?

v16.13.0

What database are you using?

postgis/postgis:13-3.1-alpine

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying Directus?

running locally

[rijkvanzanten]

I noticed you have a status field in there too. What other fields exist in this collection?

[joselcvarela]

I just created a collection without any fields, only ID (automatically created), and have the same issue 😕

[felipe-santos]

Hi friends,
for me, fixed:

directus/app/src/modules/content/routes/item.vue

Line 299 in b3f43ff

return Object.keys(defaults.value).length > 0 || hasEdits.value;

change to:
return Object.keys(edits.value).length > 0 || hasEdits.value;

changes "defaults.value" to "edits.value"

[joselcvarela]

Hi friends, for me, fixed:

directus/app/src/modules/content/routes/item.vue

Line 299 in b3f43ff

return Object.keys(defaults.value).length > 0 || hasEdits.value;

change to: return Object.keys(edits.value).length > 0 || hasEdits.value;

changes "defaults.value" to "edits.value"

Object.keys(edits.value).length > 0 and hasEdits.value are the same, so not necessary.
The thing is: default value comes from database vendor, in this case Postgresql.

Maybe we need to differentiate default values created by users and other default values, and only do the check for default values created by user: Object.keys(defaultsByUser.value).length > 0 🤔

[rijkvanzanten]

Maybe we need to differentiate default values created by users and other default values

There's no way to differentiate between the two. They're stored and returned in the same location by the database 👍🏻

[joselcvarela]

Maybe we could ignore defaults which doesn't match the type value, for example, in this case nextval... does not match uuid so we should ignore it.

[rijkvanzanten]

Yeah! There's also an active discussion on the knex-schema-inspector around a way to split up generated default values (like nextval()) and "regular" static ones (knex/knex-schema-inspector#73) cc @Oreilles