fix: handle first-time item insertion during comparison

[rahul-arb]

Summary

This PR fixes an issue where the website item update logic fails for newly created Items because it attempts to compare the current document with a previous version that does not exist.

Root Cause

During the initial insert, there is no previous document available. The existing comparison logic assumes one exists, resulting in an exception.

Solution

• Added a guard condition to detect first-time inserts.
• Skip the comparison when no previous document is available.
• Preserve the existing comparison behavior for document updates.

Testing

• ✅ Created a new Item and verified that no exception is raised.
• ✅ Updated an existing Item and verified that the comparison logic continues to work as expected.
• ✅ Confirmed that existing functionality remains unchanged for update operations.

Fixes issue Issue no 367

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[greptile-apps]

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.
• The guarded path is only inside the existing Website Item sync block.
• Normal updates still compare against the previous Item document before syncing fields.

Important Files Changed

Filename	Overview
webshop/webshop/crud_events/item/update_website_item.py	Adds a defensive return before comparing editable Item fields when no previous document is available.

_{Reviews (1): Last reviewed commit: "fix: handle first-time item insertion du..." | Re-trigger Greptile}