fix(dashboard): Make preferences.default a nullable field

[desiprisg]

What changed? Why was the change needed?

Screenshots

Expand for optional sections

Related enterprise PR

Special notes for your reviewer

[linear]

NV-4814 🐛 Autosave doesn't save workflow name

[netlify]

✅ Deploy Preview for novu-stg-vite-dashboard-poc ready!

Name	Link
🔨 Latest commit	ed0b257
🔍 Latest deploy log	https://app.netlify.com/sites/novu-stg-vite-dashboard-poc/deploys/673cb5541971750008c83ca6
😎 Deploy Preview	https://deploy-preview-7068--novu-stg-vite-dashboard-poc.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[rifont]

The default preferences isn't nullable, it should always be present. The default preferences for Dashboard-sourced workflows will always be the DEFAULT_WORKFLOW_PREFERENCES, whereas the default preferences for Framework-sourced workflows are that defined in code.

What issue is this solving?

[rifont]

If no default preferences are supplied, the UpsertWorkflow use-case falls back to DEFAULT_WORKFLOW_PREFERENCES here. So instead, we should not send default.

[rifont]

With the current API validation and implementation, there are no cases where default preferences will be persisted as null. The frontend always calls the PUT /v2/workflows/{id} endpoint with the object retrieved from GET /v2/workflows{id}, so we can safely close this PR.

Any cases where the default: null issue arose are from a previous broken implementation during development of Dashboard V2, and should be considered "corrupt".