search

payloadcms / payload

Payload is the open-source, fullstack Next.js framework, giving you instant backend superpowers. Get a full TypeScript backend and admin panel instantly. Use Payload as a headless CMS or for building powerful applications.
https://payloadcms.com
MIT License
28.21k stars 1.75k forks source link

defaultValue is ignored when creating a doc from "Add new" on a join field. #8612

Closed energee closed 3 days ago

energee commented 1 month ago

Link to reproduction

No response

Environment Info

Node: 22.9.0 npm: 10.8.3 Yarn: 1.22.22 pnpm: 9.10.0 Relevant Packages: payload: 3.0.0-beta.111 next: 15.0.0-canary.173 @payloadcms/db-mongodb: 3.0.0-beta.111 @payloadcms/graphql: 3.0.0-beta.111 @payloadcms/next/utilities: 3.0.0-beta.111 @payloadcms/richtext-lexical: 3.0.0-beta.111 @payloadcms/translations: 3.0.0-beta.111 @payloadcms/ui/shared: 3.0.0-beta.111 react: 19.0.0-rc-3edc000d-20240926 react-dom: 19.0.0-rc-3edc000d-20240926

Describe the Bug

defaultValue setting appears to not work when generating a new doc from a join field.

Reproduction Steps

Set a defaultValue on a collection -> Test by creating a new item -> Try creating a new item from a join field ("Add New" or "Create New " button), field will be blank.

Adapters and Plugins

db-mongodb

akhrarovsaid commented 1 month ago

Hey @energee,

I believe this is happening because these lines are preventing this function from being called due to the predicate above it. I plan to have a PR out soon, hopefully by tonight. Seems I'm close to a fix.

akhrarovsaid commented 1 month ago

Hey @energee,

Thanks for your patience - I have a PR up for this.

akhrarovsaid commented 1 week ago

Hey @energee,

I've closed my PR as I'm no longer able to reproduce this issue in the monorepo as of beta.128. Try updating your Payload packages and test if you're still experiencing default values not populating?

Edit: See here https://github.com/user-attachments/assets/a5b4b75d-757d-4c51-a385-acc094c89add

jacobsfletch commented 3 days ago

I'm no longer able to reproduce this issue in the monorepo as of beta.128.

Same. Thanks again for confirming @akhrarovsaid 🙏

github-actions[bot] commented 1 day ago

This issue has been automatically locked. Please open a new issue if this issue persists with any additional detail.