Incorrect @default Comments in BaseKitOptions Interface

[MohamedElGhandour]

Description:

There is an inconsistency in the comments for the @default values in the BaseKitOptions interface. Specifically, the comments indicate that certain options have a default value of true, while the actual default value in the code is set to false.

For example:

• Current code: document:false, text: false, gapcursor: false, etc.
• Current comment: @default true

Steps to Reproduce:

1. Open the BaseKitOptions interface in the codebase.
2. Observe that many options (such as document, text, gapcursor, etc.) have the @default true comment, even though their default value is false.

Expected Behavior:

The @default comments should correctly reflect the actual default values in the code.

Actual Behavior:

The comment for options like document, text, gapcursor, and others state that their default value is true, but the actual value is false.

Suggested Fix:

Update the comments to correctly represent the default values:

• Change @default true to @default false for options that default to false.

Example:

/**
 * @default false
 */
document: false

/**
 * @default false
 */
text: false

/**
 * @default false
 */
gapcursor: false

Why is this important?

• Clear and accurate documentation helps developers understand the expected behavior without needing to dig into the code.

• It prevents confusion when working with these options and makes the code more maintainable.