Discussion on using `initialValue` support for all `type`s and possibility of supporting `slug`-like `options.source` handling for `initialValue` fields.

Just noticed that

initialValue

support launched for all `type`s 🎉 very very cool
Related question: is it possible (or on the roadmap) to support

slug

-like

options.source

handling for

initialValue

fields? I’d like to be able to, say, source a document field value for the

initialValue

of an

object

within the parent document.

Interesting question - maybe knows the answer to this

Super interesting question! I'm going to ask some folks on the dev team. Theoretically a bunch of things are possible, since you can give a function as an initialValue, but I don't know if there's any first-party support for grabbing a field off the document (like slug's options or preview's

select

...)
I'm working on expanding the initial value docs, so i'll explore this a bit, and ask around (either way, it's totally a use case I can see being helpful and i'll put it into some folks ears
😄 )

Thanks for the responses 🙂
Example use case: I’d like to manage a blog article “hero” section

blogPost.title

separately from the SEO

blogPost.seoTitle

to allow for slight differences. But I’m thinking it could be cool for a user to enter a

blogPost.title

and it would prefill

seoTitle

field as a default.

Ahhh, that might not end up working out with initial values. Initial Values only come into play upon a new document creation
We can get that done in a couple other ways, though!

You could manage this with a conditional in your query. I'd have to play a bit to get the exact query but it would look something like this:

You could also create a custom input with a button to generate the text (like the slug input would do).

I think handling it in the data layer makes the most sense, but either way should work

Ahhh, that might not end up working out with initial values. Initial Values only come into play upon a new document creation
We can get that done in a couple other ways, though!

You could manage this with a conditional in your query. I'd have to play a bit to get the exact query but it would look something like this:

You could also create a custom input with a button to generate the text (like the slug input would do).

I think handling it in the data layer makes the most sense, but either way should work

You could also create a custom input with a button to generate the text (like the slug input would do).

Yeah was thinking I might just go this route 😛 thanks for the thoughts!

You could also create a custom input with a button to generate the text (like the slug input would do).

Yeah was thinking I might just go this route 😛 thanks for the thoughts!

You might also look at a Custom Document Action: https://www.sanity.io/docs/document-actions#362c883e4421
On publish -> check if seoTitle exists -> if not, set it to title value