FYI, as an ugly workaround, I'm handling the onCreate event, and doing this for the time being:

const { state, view } = props.editor

if (state.plugins.length > 0) {
    const restOfPlugins: Plugin[] = []
    const suggestionPlugins: Plugin[] = []

    state.plugins.forEach((plugin) => {
        // eslint-disable-next-line @typescript-eslint/ban-ts-comment
        // @ts-ignore: The `Plugin` type does not include `key`
        if ((plugin.key as string).includes('Suggestion')) {
            suggestionPlugins.push(plugin)
        } else {
            restOfPlugins.push(plugin)
        }
    })

    view.updateState(
        state.reconfigure({
            plugins: [...suggestionPlugins, ...restOfPlugins],
        }),
    )
}

Would love it if something akin to the extension priorities was possible for these ProseMirror plugins, so we can pick the ones we need to have a higher priority than the built-in ones, like the input rules.

FYI, as an ugly workaround, I'm handling the onCreate event, and doing this for the time being:

const { state, view } = props.editor

if (state.plugins.length > 0) {
    const restOfPlugins: Plugin[] = []
    const suggestionPlugins: Plugin[] = []

    state.plugins.forEach((plugin) => {
        // eslint-disable-next-line @typescript-eslint/ban-ts-comment
        // @ts-ignore: The `Plugin` type does not include `key`
        if ((plugin.key as string).includes('Suggestion')) {
            suggestionPlugins.push(plugin)
        } else {
            restOfPlugins.push(plugin)
        }
    })

    view.updateState(
        state.reconfigure({
            plugins: [...suggestionPlugins, ...restOfPlugins],
        }),
    )
}

Would love it if something akin to the extension priorities was possible for these ProseMirror plugins, so we can pick the ones we need to have a higher priority than the built-in ones, like the input rules.

I also encountered this problem, But I don't see how to use this solution.
Maybe I'm a rookie
So could you explain it in detail? Thank you very much！！！

@cmcQDGCS You have to put that code in the onCreate event handler that you can attach to useEditor hook (assuming you're using React).

@rfgamaral Thank you for your reply, No wonder I can't understand it. I use Vue. I'll study it again

It shouldn't matter what you use... In the same place you pass the extensions to use, handle the onCreate event there.

@rfgamaral owowow！！I know what you mean！
but....When I went to loop editor plugins，No ”suggestion“

@cmcQDGCS We have multiple mention-like extensions, and we named them all with "suggestion" in the name (we don't use the official mention extension). You have to adapt that part to your needs. It seems you're using the official one, so changing (plugin.key as string).includes('Suggestion') to (plugin.key as string).includes('mention'), should work for you.

@rfgamaral I tried, but I still haven't solved it...I don't know why.
But thank you very very very much for your answer
Maybe I'm too stupid. My understanding of tiptap is very shallow

Start explaining exactly what you're doing, and the problem you're having? Try to create a CodeSandbox minimal example, and explain the issue you're having.

@rfgamaral
https://codesandbox.io/s/wizardly-wiles-od132h?file=/src/components/editor.vue
Enter a # selection prompt in the editor

Tried to take a look, but I can't figure out what's wrong... Maybe you were right, and Vue works different on how it initializes the editor, which is having an impact on this. Maybe @bdbch can provide more insight here. Sorry, I'm a React developer, I barely know anything about Vue.

Thank you very much for your help. I'll go and have a deep understanding

@rfgamaral does the priority have any effect on that issue?

@rfgamaral does the priority have any effect on that issue?

I don't think it does because the problem here lies in the ProseMirror plugins priority, and not the Tiptap extensions priority (which are 2 different things). As I've suggested in the OP, I think we need a way to override the priority for ProseMirror plugins, akin to the Extensions priority field.

@rfgamaral pointed it out well here. Right now you'd have to fallback to a dirty solution. I think a way to override the priorities of loaded ProseMirror plugins would be a neat way to solve this issue.

@Cuimc I'll take a look at your sandbox but have to say I'm also not a primary Vue developer.

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 7 days

This is really painful. Is there any easier workaround for this?

Hi there, just ran into this now. Here's how I fixed this on my end. I'm using Vue tiptap but I think this should work for everyone. Here's some context so you know if this applies to you as well.

• I don't want enter to apply to heading markdown, only spaces.

What I did is extend the heading extension, modify the input rule to only support spaces after the #.

Heading.extend({
    addInputRules() {
        return this.options.levels.map((level) => {
            return textblockTypeInputRule({
-                find: new RegExp(`^(#{1,${level}})\\s$`),
+                find: new RegExp(`^(#{1,${level}}) $`),
                type: this.type,
                getAttributes: {
                    level,
                },
            })
        })
    },
})

@jaggy The cleanest solution here, I guess this issue is resolved.

I put more doc for the rookies

import {  useEditor,  textblockTypeInputRule } from '@tiptap/react';

// ...

useEditor({
   extensions: [
        Heading.extend({
          addInputRules() {
            return this.options.levels.map((level: number) => {
              return textblockTypeInputRule({
                find: new RegExp(`^(#{1,${level}}) $`),
                type: this.type,
                getAttributes: {
                  level,
                },
              })
            })
          },
        }),
        StarterKit.configure({
          heading: false,
        })
    ]
})