Singleton with translations

[jdwillemse]

I'm trying to combine this plugin with the setup for singleton document described here. When I do this the translation tab disappears across all documents. I'm using document level translations.

Assuming the settings document needs to be translated too, how do I rewrite this to make it work?

import S from "@sanity/desk-tool/structure-builder";
 
export default () =>
  S.list()
    .title('Content')
    .items([
      S.listItem()
        .title('Site settings')
        .child(
          S.document()
            .schemaType('siteSettings')
            .documentId('siteSettings')
        ),
      // Add a visual divider (optional)
      S.divider(),
      // List out the rest of the document types, but filter out the config type
      ...S.documentTypeListItems()
        .filter(listItem => !['siteSettings'].includes(listItem.getId()))
    ])

[LiamMartens]

So technically the problem is that when translating documents you are creating new ones, which conflicts with the whole singleton thing. However I did find a way around it as follows:

import S from '@sanity/desk-tool/structure-builder';
import homepage from './schemas/homepage';
import * as Structure from 'sanity-plugin-intl-input/lib/structure';

export const getDefaultDocumentNode = (props) => {
  return Structure.getDefaultDocumentNode(props);
};

export default () => {
  return S.list()
    .id('__root__')
    .title('Content')
    .items([
      S.listItem()
        .id('siteSettings')
        .title('Site Settings')
        .schemaType('siteSettings')
        .child(
          S.documentList()
            .id('siteSettings')
            .title('Site Settings')
            .schemaType('siteSettings')
            .filter('_id == $id && _type == $type')
            .params({
              id: 'siteSettings',
              type: 'siteSettings',
            })
            .menuItems([
              {
                title: 'Create new',
                intent: {
                  type: 'create',
                  params: {
                    id: 'siteSettings',
                    type: 'siteSettings',
                    template: 'siteSettings'
                  }
                }
              }
            ])
        ),
        ...Structure.getFilteredDocumentTypeListItems().filter(l => !['siteSettings'].includes(l.getId())),
    ])
};

Some explanation to this:
Basically we are keeping the same structure as usual so Sanity can resolve the structure for non-singleton's (which means a url like /desk/documentType/documentId)
But in the document list we are only showing the document with id siteSettings (hence we will always only show a single document). Now when this document does not exist yet, we will need a way to create it, but only the one with the fixed id. To do this we can create a menu item with the intent to create a document with a fixed id. This way everything should work as expected and you will still keep the singleton-like behavior.

Let me know if this works for you!

Example below

[jdwillemse]

Thanks for getting back to me on this issue.

The solution you propose is essentially the same as the default option. It is still possible to create multiple of the singleton doc and the user has to click through a secondary document list of one item. I'm trying to avoid the list view completely so clicking the content type leads directly to the page.

I understand why this tricky with the intl plugin, but singletons are a very standard part of all our projects so I'll need to keep looking for a solution.

Thanks again for the help

[LiamMartens]

@jdwillemse No you can still only create the one with the fixed ID (aka singleton) because the "Create new" action is fixed to the ID with this structure. However I am aware it is slightly more cumbersome. I am talking to some guys at Sanity regarding conflicts with custom desk structure but have not been able to find a resolution yet.

[tom2strobl]

@LiamMartens I'm trying to use it as you suggest up there (even though the extra pane for the single document is really weird/ugly), but I'm actually running into the issue of editor/translations-tabs not showing up on the singleton, even with your suggested solution.

This is my deskStructure (the commented out part is how I would have included the singleton without the intl-plugin, ignore the base settings, these are non-i18n):

import S from '@sanity/desk-tool/structure-builder'
import * as Structure from 'sanity-plugin-intl-input/lib/structure'

export const getDefaultDocumentNode = (props) => {
  if (props.schemaType === 'page') {
    return S.document().views(Structure.getDocumentNodeViewsForSchemaType(props.schemaType))
  }
  return S.document()
}

export default () => {
  const items = Structure.getFilteredDocumentTypeListItems()
  return S.list()
    .title('Content')
    .items([
      S.listItem().title('Base Settings').icon(GlobalIcon).child(S.document().schemaType('base').documentId('base')),

      // S.listItem()
      //   .title('Global Settings')
      //   .icon(HomeIcon)
      //   .child(S.document().schemaType('global').documentId('global')),

      S.listItem()
        .id('global')
        .title('Global Settings')
        .icon(HomeIcon)
        .schemaType('global')
        .child(
          S.documentList()
            .id('global')
            .title('Global Settings')
            .schemaType('global')
            .filter('_id == $id && _type == $type')
            .params({
              id: 'global',
              type: 'global'
            })
            .menuItems([
              {
                title: 'Create new',
                intent: {
                  type: 'create',
                  params: {
                    id: 'global',
                    type: 'global',
                    template: 'global'
                  }
                }
              }
            ])
        ),

      S.divider(),

      ...items.filter((item) => !['base', 'global'].includes(item.spec.id))
    ])
}

Since i18n works on other schemas in the same project and I'm using a global config with i18n: true, I'm kinda confident the config is fine (it's using GROQ for the languages property if that makes a difference for the singleton?).

[tom2strobl]

I guess the other way to do it is to nest all document fields into one object and throwing options: { i18n: true } on it. Although it seems like it kills fieldset borders and does some padding/margin-weirdness (https://www.dropbox.com/s/g5bp6u1aodnqpej/Screenshot%202020-07-28%2016.11.10.png?dl=0)

[ylokesh]

@LiamMartens @tom2strobl I am facing same issue where in, Translation tab disappears for article documents appearing 2 levels deep.

Any pointers would be really helpful.

PS: I have tried the approach given above but it somehow it didn't work for me.

export default () => {
	return S.list()
		.id('__root__')
		.title('Content')
		.items([
		S.divider(),
		S.listItem()
			.title('Articles')
			.icon(FaNewspaper)
			.child(
			S.list()
				.title('Article Type')
				.items([
					getArticlePreviews('featureArticle').title('Feature'),
					getArticlePreviews('galleryArticle').title('Gallery'),
					getArticlePreviews('howToArticle').title('How To')
				])
			)]
		)
}

const getArticlePreviews = type =>
	S.documentTypeListItem(type).child(
		S.documentTypeList(type).child(docId =>
		S.document()
			.id(docId)
			.schemaType(type)
			.views([
			S.view.form()
			])
		)
	)

[saulhardman]

Although it seems like it kills fieldset borders and does some padding/margin-weirdness (https://www.dropbox.com/s/g5bp6u1aodnqpej/Screenshot%202020-07-28%2016.11.10.png?dl=0)

I'm experiencing the same issue and I'm wondering what the solution is? Do we need to write (or overwrite) a custom component for nested objects like this?

Any help pointing us in the right direction would be great @LiamMartens 👍

[LiamMartens]

@saulhardman Sorry I have not been able to look into this deeper. I might have to update the component that's being used as it is most likely outdated according to updates Sanity has received now. I try to look at it this week.

[LiamMartens]

@ylokesh I need to have a look at this 😬 combining desk structures is a bit "hacky" at the moment Imo

[saulhardman]

@LiamMartens no need to apologise – thanks for taking a look and let us know if there's any way we can help out.

[LiamMartens]

@ylokesh you also have the getDefaultDocumentNode export in your deskStructure?

[LiamMartens]

@tom2strobl very late answer but in your case I believe it is because of your getDefaultDocumentNode export. You are limiting it to the "page" schemaType, but your document has a "global" schemaType

[LiamMartens]

@saulhardman I published a beta version 5.1.0-beta.0 where I updated the component to be in line with the latest Sanity updates. I need to do some more testing before releasing but it's there

[saulhardman]

@saulhardman I published a beta version 5.1.0-beta.0 where I updated the component to be in line with the latest Sanity updates. I need to do some more testing before releasing but it's there

Hi @LiamMartens, thank you very much 👍 I'll try that version out and get back to you.