Additional Document Actions

[raulsaavedrax]

Hello everyone!
I want to migrate a custom document action from V2 to V3. I followed this guide.

However, I don't want to replace the Publish Action, but instead add an additional one named Preview Article, so it has the following behavior:

In V3, instead of adding the additional action to the dropdown, it replaces the Publish Action, when I would like the publish one to be the main one.

Here is how I moved my v2 code to the new v3 code.

V2

import defaultResolve from 'part:@sanity/base/document-actions';

import { PreviewBlogArticleAction } from './PreviewBlogArticleAction';

export default function resolveDocumentActions(props) {
  return [...defaultResolve(props), PreviewBlogArticleAction];
}

V3

// inside defineConfig({})
document: {
  actions: (prev) => {
    return [...prev, PreviewBlogArticleAction];
  },
},

I also tried to create a custom Publish Action following the guide above along my new action to work around this, but I see that PublishAction is not exported anymore as of the new release candidate version. (sanityv3.0.0-rc.0)

What I am doing wrong? or is the new actions API only meant to replace predefined actions?

[geball]

Hi @raulsaavedrax. Please take a look at this reply, which gives some context and also offers a workaround to access the array of document actions. In your case, you would want to modify the map so as not to filter out the default Publish action, but the approach should be similar.

[raulsaavedrax]

This fixed it for me 💯 Thank you! @geball