Fixed docs for renaming modules in ckeditor5-fullscreen.

Author: martnpaneq

packages/ckeditor5-fullscreen/docs/features/fullscreen.md

@@ -168,15 +168,15 @@ Below you will find a customized demo:
 
 This section covers how to provide fullscreen mode integration for other {@link getting-started/setup/editor-types editor types} than classic and decoupled. Please note that only these two editor types are officially supported, so the code snippets below are exemplary and may not solve all technical challenges.
 
-First, you need to create a custom class extending {@link module:fullscreen/handlers/abstracteditorhandler~AbstractEditorHandler `AbstractEditorHandler`}. Besides the optional typing improvements, the most important thing is to implement its custom {@link module:fullscreen/handlers/abstracteditorhandler~AbstractEditorHandler#defaultOnEnter `#defaultOnEnter()`} method. It should move the editor UI elements proper for your editor type to the fullscreen container, preferably using {@link module:fullscreen/handlers/abstracteditorhandler~AbstractEditorHandler#moveToFullscreen `#moveToFullscreen()`} helper - it will assure the elements are moved back in DOM when leaving fullscreen mode.
+First, you need to create a custom class extending {@link module:fullscreen/handlers/abstracteditorhandler~FullscreenAbstractEditorHandler `FullscreenAbstractEditorHandler`}. Besides the optional typing improvements, the most important thing is to implement its custom {@link module:fullscreen/handlers/abstracteditorhandler~FullscreenAbstractEditorHandler#defaultOnEnter `#defaultOnEnter()`} method. It should move the editor UI elements proper for your editor type to the fullscreen container, preferably using {@link module:fullscreen/handlers/abstracteditorhandler~FullscreenAbstractEditorHandler#moveToFullscreen `#moveToFullscreen()`} helper - it will assure the elements are moved back in DOM when leaving fullscreen mode.
 
 Then, in the editor's `toggleFullscreen` command, you will need to substitute the {@link module:fullscreen/fullscreencommand~FullscreenCommand#fullscreenHandler `#fullscreenHandler`} property with an instance of your custom class. It can be done by adding a custom plugin that should be later added to the editor configuration (see the full example below).
 
 ```ts
-import { AbstractEditorHandler, FullscreenEditing } from '@ckeditor/ckeditor5-fullscreen';
+import { FullscreenAbstractEditorHandler, FullscreenEditing } from '@ckeditor/ckeditor5-fullscreen';
 import { Plugin } from 'ckeditor5/src/core';
 
-class CustomEditorHandler extends AbstractEditorHandler {
+class CustomEditorHandler extends FullscreenAbstractEditorHandler {
 	// It's not mandatory to override `#_editor` property, but that will help TypeScript to properly handle the class.
 	// Skip if you are not using TS.
 	protected override readonly _editor: CustomEditorClass;

packages/ckeditor5-fullscreen/src/fullscreencommand.ts

@@ -31,11 +31,12 @@ export class FullscreenCommand extends Command {
 	 * Specialized class handling the fullscreen mode toggling for a specific editor type.
 	 *
 	 * If you want to add support for a new editor type (for now, only Classic and Decoupled editors are handled),
-	 * create a custom handler that extends `AbstractEditorHandler` and replace `fullscreenHandler` with it after editor initialization:
+	 * create a custom handler that extends `FullscreenAbstractEditorHandler` and replace `fullscreenHandler` with it after
+	 * editor initialization:
 	 *
 	 * ```ts
-	 * // See the details of how to implement a custom handler in the `AbstractEditorHandler` class API docs.
-	 * class CustomEditorHandler extends AbstractEditorHandler {}
+	 * // See the details of how to implement a custom handler in the `FullscreenAbstractEditorHandler` class API docs.
+	 * class CustomEditorHandler extends FullscreenAbstractEditorHandler {}
 	 *
 	 * CustomEditorClass.create( document.querySelector( '#editor' ), {} )
 	 * 	.then( ( editor ) => {
@@ -57,7 +58,7 @@ export class FullscreenCommand extends Command {
 
 		// Choose the appropriate handler based on the editor type.
 		// Currently only `ClassicEditor` and `DecoupledEditor` are supported. For other editor types, you should create a custom handler
-		// that extends `AbstractEditorHandler` and replace `fullscreenHandler` with it.
+		// that extends `FullscreenAbstractEditorHandler` and replace `fullscreenHandler` with it.
 		if ( isClassicEditor( editor ) ) {
 			this.fullscreenHandler = new FullscreenClassicEditorHandler( editor );
 		} else if ( isDecoupledEditor( editor ) ) {

packages/ckeditor5-fullscreen/src/handlers/abstracteditorhandler.ts

@@ -24,8 +24,8 @@ const DIALOG_OFFSET = 28;
  * or if you wish to heavily customize the default behavior.
  *
  * The only method that is necessary to provide when extending this class is {@link #defaultOnEnter}. However, make sure to
- * familiarize yourself with the below full list of actions taken by `AbstractEditorHandler` to understand what is covered by default,
- * and what should be provided by you.
+ * familiarize yourself with the below full list of actions taken by `FullscreenAbstractEditorHandler` to understand
+ * what is covered by default, and what should be provided by you.
  *
  * When entering the fullscreen mode, the {@link #enable} method is called. It creates the properly styled container
  * and handles the editor features that need it, in the following order: