Creating a UML permission field with preset values in Sanity Studio

how would you recommend creating a UML permission field called permission that has 4 preset values corresponding to [public, private, protected, package] ? In the schema

you can use something like :_experimental_actions: [ /*'create', 'update', 'delete', 'publish*/
],

thanks for both options - the second one is required by my LRM schemas

p.s. what is this ticket thingo?

It's the way track tickets within Slack. We have a write-up on it here !

Neat. And a sanity powered bot is also fascinating!?

That's one of the coolest things about Sanity to me. Because of the APIs and how unopinionated it is about how your content is used you can do some really cool stuff!

I have a bot project on the back-burner, perhaps I’ll fast track it.

p.s. I think you might want to put this answer in the snippets part of the sanity site. Perhaps also add it to the schema docs.

p.s. I think you might want to put this answer in the snippets part of the sanity site. Perhaps also add it to the schema docs.

I've been thinking about that for the last few weeks, actually. Determining which schema to use for which purpose can sometimes be a bit opaque when you're new to the Studio. These things are documented, but it's usually buried in the middle of optional parameters and can be very easily overlooked. We need to either provide a guide in the Getting Started section or supplement the existing docs with more examples that are easier to understand.

I leaned mostly from the schemas created by the cli,

Ah, like one of the options you can select when you bootstrap a new project with

sanity init

?

but I also read the schema docs a few times

yes

Got it. I wonder if creating an option for some sort of 'everything' studio that has all of these examples would also be helpful in that case.

It would

I kind of made one like that

Thank you for the feedback! It's super helpful!

I then started over to learn about template integration

but I got tons of schemas in that studio.

there was some interesting localization examples in the e-commerce one

I have a list of questions in faqs within helpArticles in that datasets.

Here are a couple:

1. can I set options to show the category document type as a nested tree (extra points for a filter control). I guess the media plugins do it with custom react code.

2. When I have a reference field (say to a category) and the category does not exist could I add an option to create it (in a model dialog window perhaps)?

2. When I have a reference field (say to a category) and the category does not exist could I add an option to create it (in a model dialog window perhaps)?

For your second question, the answer is 'soon'! It's one of our most requested features and we are actively looking for a solution. For your first, I think I'm not understanding it correctly, can you elaborate so that hopefully I get it 🙂 ?

great

I have a category schema with a reference field called patent. (which I got from the docs I think)

I’d like to have a better editing experience with this category document - I’d like to see children under their parent using a tree or nested lists instead of a list (in the second column of the desk)

and I’d like to filter by children of design pattern (used in the pattern catalog) or by children of fullStack (used in the post)

I know it is possible to filter in a reference field.

and I’d like to filter by children of design pattern (used in the pattern catalog) or by children of fullStack (used in the post)

something like: