Add context option to SvelteNodeViewRenderer

[kuruczg444]

Currently there is no way to make contexts defined outside the Editor instance available for custom extensions.

With this little change, it's now possible to use Svelte's getAllContexts function to pass them to the custom extensions. Here's an example:

Editor.svelte

<script lang="ts">
  import { getAllContexts, onMount } from 'svelte';
  import type { Readable } from 'svelte/store';
  import { createEditor, Editor, EditorContent } from 'svelte-tiptap';
  import StarterKit from '@tiptap/starter-kit';
  import MyCustomExtension from './MyCustomExtension';

  let editor = $state() as Readable<Editor>;

  const allContexts = getAllContexts();

  onMount(() => {
    editor = createEditor({
      extensions: [StarterKit, MyCustomExtension(allContexts)],
      content: `Hello world!`,
    });
  });
</script>

<EditorContent editor={$editor} />

MyCustomExtension.ts

import { Node } from '@tiptap/core';
import { SvelteNodeViewRenderer } from 'svelte-tiptap';
import MyCustomComponent from './MyCustomComponent.svelte';

export default (context: Map<any, any>) => Node.create({
  // ...
  addNodeView() {
    return SvelteNodeViewRenderer(MyCustomComponent, { context });
  },
  // ...
})

[sibiraj-s]

haven't checkout the code yet. shouldn't this be string, unknown?

[kuruczg444]

I used the default ReturnType of getAllContexts: https://svelte.dev/docs/svelte/svelte#getAllContexts which is Map<any, any>.

As contexts are not directly accessed anyway, I believe the type here is not really relevant other than it being a Map.

However, string is definitely not correct as Map keys in Svelte can also be Symbols.

The better pattern to access contexts are documented in the Svelte docs

[sibiraj-s]

Mentioned just for the sake of eslint. planning to import some shared configuration where any is explicitly avoided. might have to exclude this line, hence said

[kuruczg444]

Maybe ReturnType<typeof getAllContexts> could be used to not use any any.