🐛 fix(docs): resolve code indentation error due to a wrong push that reverted some files (medium severity incident affecting documentation codeblocks)

Author: zRelaxz

en/cli/cli-database.mdx

@@ -140,8 +140,8 @@ The exact files vary by ORM but the layout follows the same convention for every
 Once the command finishes, you can inject _DatabaseService_ into any handler, guard, or service within the same module scope. The service is exported from the database module, so importing _DatabaseModule_ in any other module gives you access to it through the DI container.
 
 ```typescript filename="src/modules/hello/hello.service.ts"
-import { Injectable } from "@spraxium/common";
-import { DatabaseService } from "../database/database.service";
+import { Injectable } from '@spraxium/common';
+import { DatabaseService } from '../database/database.service';
 
 @Injectable()
 export class HelloService {

en/cli/cli-dev.mdx

@@ -24,9 +24,9 @@ spraxium dev
 ```typescript filename="spraxium.config.ts"
 export default {
   dev: {
-    entrypoint: "src/main.ts",
-    include: ["src/**"],
-    exclude: ["src/**/*.spec.ts"],
+    entrypoint: 'src/main.ts',
+    include: ['src/**'],
+    exclude: ['src/**/*.spec.ts'],
     debounce: 300,
   },
 };

en/components/components-buttons.mdx

@@ -49,7 +49,11 @@ A static button is the simplest interactive component. You decorate a class with
 import { Button } from '@spraxium/components';
 
 @Button({
-customId: 'confirm_action', label: 'Confirm', style: 'success', emoji: '✅', })
+  customId: 'confirm_action',
+  label: 'Confirm',
+  style: 'success',
+  emoji: '✅',
+})
 export class ConfirmButton {}
 
 ````
@@ -129,12 +133,12 @@ The handler class must be decorated with _@ButtonHandler_ and pass the component
 Link buttons open a URL in the user's browser without firing any handler on the bot side. They are useful for directing users to documentation, dashboards, or external tools. Because Discord requires a different button style for links, the _@LinkButton_ decorator omits _customId_ and _style_ in favor of a _url_ field.
 
 ```typescript filename="src/components/buttons/docs-link.button.ts"
-import { LinkButton } from "@spraxium/components";
+import { LinkButton } from '@spraxium/components';
 
 @LinkButton({
-  url: "https://docs.example.com",
-  label: "View Documentation",
-  emoji: "📖",
+  url: 'https://docs.example.com',
+  label: 'View Documentation',
+  emoji: '📖',
 })
 export class DocsLinkButton {}
 ```
@@ -176,13 +180,13 @@ _ButtonService_ is the injectable service that transforms decorated classes into
 </Callout>
 
 ```typescript filename="src/commands/moderation.command-handler.ts"
-import { Ctx, SlashCommandHandler } from "@spraxium/common";
-import { ButtonService, ContextService } from "@spraxium/components";
-import type { ChatInputCommandInteraction } from "discord.js";
-import { ConfirmButton } from "../components/buttons/confirm.button";
-import { CancelButton } from "../components/buttons/cancel.button";
-import { DocsLinkButton } from "../components/buttons/docs-link.button";
-import { ModerationCommand } from "./moderation.command";
+import { Ctx, SlashCommandHandler } from '@spraxium/common';
+import { ButtonService, ContextService } from '@spraxium/components';
+import type { ChatInputCommandInteraction } from 'discord.js';
+import { ConfirmButton } from '../components/buttons/confirm.button';
+import { CancelButton } from '../components/buttons/cancel.button';
+import { DocsLinkButton } from '../components/buttons/docs-link.button';
+import { ModerationCommand } from './moderation.command';
 
 @SlashCommandHandler(ModerationCommand)
 export class ModerationCommandHandler {
@@ -192,7 +196,7 @@ export class ModerationCommandHandler {
   ) {}
 
   async handle(@Ctx() interaction: ChatInputCommandInteraction): Promise<void> {
-    const ctx = await this.context.create({ targetUserId: "123456" });
+    const ctx = await this.context.create({ targetUserId: '123456' });
     const actionRow = this.buttons.rowWithContext(
       ctx,
       ConfirmButton,
@@ -201,7 +205,7 @@ export class ModerationCommandHandler {
     const linkRow = this.buttons.build(DocsLinkButton);
 
     await interaction.reply({
-      content: "Review the moderation action below.",
+      content: 'Review the moderation action below.',
       components: [actionRow, linkRow],
     });
   }
@@ -256,10 +260,10 @@ The _style_ field accepts one of four named values that map to Discord's _Button
 Only handler classes need to be registered, and they go in the _handlers_ array of your feature module. Component classes decorated with _@Button_ or _@LinkButton_ are metadata-only and are never added to any module. The dispatcher reads their customId and configuration directly from the class reference stored inside each _@ButtonHandler_ decorator, with no DI instantiation required.
 
 ```typescript filename="src/modules/moderation/moderation.module.ts"
-import { Module } from "@spraxium/common";
-import { ConfirmButtonHandler } from "./components/confirm.handler";
-import { CancelButtonHandler } from "./components/cancel.handler";
-import { UserBanButtonHandler } from "./components/user-ban.handler";
+import { Module } from '@spraxium/common';
+import { ConfirmButtonHandler } from './components/confirm.handler';
+import { CancelButtonHandler } from './components/cancel.handler';
+import { UserBanButtonHandler } from './components/user-ban.handler';
 
 @Module({
   handlers: [ConfirmButtonHandler, CancelButtonHandler, UserBanButtonHandler],

en/components/components-context.mdx

@@ -20,11 +20,11 @@ The flow context system is shared across all component types. A context created
 Inject _ContextService_ into your command or service and call _create_ with the data object you want to thread through the flow. The method returns a _SpraxiumContext_ with a generated UUID, the data, timestamps, and the TTL. You then pass this context to the component service's build method.
 
 ```typescript filename="src/commands/setup-wizard.command-handler.ts"
-import { Ctx, SlashCommandHandler } from "@spraxium/common";
-import { ContextService, ButtonService } from "@spraxium/components";
-import type { ChatInputCommandInteraction } from "discord.js";
-import { NextStepButton } from "../components/next-step.button";
-import { SetupWizardCommand } from "./setup-wizard.command";
+import { Ctx, SlashCommandHandler } from '@spraxium/common';
+import { ContextService, ButtonService } from '@spraxium/components';
+import type { ChatInputCommandInteraction } from 'discord.js';
+import { NextStepButton } from '../components/next-step.button';
+import { SetupWizardCommand } from './setup-wizard.command';
 
 @SlashCommandHandler(SetupWizardCommand)
 export class SetupWizardCommandHandler {
@@ -42,7 +42,7 @@ export class SetupWizardCommandHandler {
     const row = this.buttons.rowWithContext(ctx, NextStepButton);
 
     await interaction.reply({
-      content: "Welcome to the setup wizard. Click Next to begin.",
+      content: 'Welcome to the setup wizard. Click Next to begin.',
       components: [row],
     });
   }
@@ -116,10 +116,10 @@ The _SpraxiumContext_ object carries both your custom data and operational metad
 Use the _@FlowContext()_ parameter decorator in your handler's _handle_ method to receive the resolved context. The dispatcher extracts the context ID from the _customId_, retrieves the context from the storage adapter, validates expiration and user restrictions, and injects the resolved object. If the context has expired or the user is restricted, the dispatcher replies with the configured error message and does not invoke the handler.
 
 ```typescript filename="src/components/next-step.handler.ts"
-import { ButtonHandler, Ctx, FlowContext } from "@spraxium/components";
-import type { ButtonInteraction } from "discord.js";
-import type { SpraxiumContext } from "@spraxium/components";
-import { NextStepButton } from "./next-step.button";
+import { ButtonHandler, Ctx, FlowContext } from '@spraxium/components';
+import type { ButtonInteraction } from 'discord.js';
+import type { SpraxiumContext } from '@spraxium/components';
+import { NextStepButton } from './next-step.button';
 
 interface WizardData {
   step: number;
@@ -147,11 +147,11 @@ export class NextStepButtonHandler {
 The _ContextService.update_ method patches the context data without replacing the entire object. This is useful in multi-step flows where each handler adds or modifies a subset of the data. The method returns a boolean indicating whether the update succeeded (context found and not expired).
 
 ```typescript filename="src/components/step-two.handler.ts"
-import { ButtonHandler, Ctx, FlowContext } from "@spraxium/components";
-import { ContextService } from "@spraxium/components";
-import type { ButtonInteraction } from "discord.js";
-import type { SpraxiumContext } from "@spraxium/components";
-import { StepTwoButton } from "./step-two.button";
+import { ButtonHandler, Ctx, FlowContext } from '@spraxium/components';
+import { ContextService } from '@spraxium/components';
+import type { ButtonInteraction } from 'discord.js';
+import type { SpraxiumContext } from '@spraxium/components';
+import { StepTwoButton } from './step-two.button';
 
 interface WizardData {
   step: number;
@@ -169,11 +169,11 @@ export class StepTwoButtonHandler {
   ): Promise<void> {
     await this.context.update<WizardData>(ctx.id, {
       step: 2,
-      settings: { ...ctx.data.settings, language: "en" },
+      settings: { ...ctx.data.settings, language: 'en' },
     });
 
     await interaction.reply({
-      content: "Step 2 complete. Proceeding to step 3.",
+      content: 'Step 2 complete. Proceeding to step 3.',
       ephemeral: true,
     });
   }
@@ -185,11 +185,11 @@ export class StepTwoButtonHandler {
 Call _ContextService.delete_ when the flow is complete or cancelled. This immediately removes the context from the storage adapter. While contexts expire automatically based on TTL, explicit deletion is good practice for flows that complete normally, as it frees storage and prevents stale data from being read in edge cases.
 
 ```typescript filename="src/components/finish-wizard.handler.ts"
-import { ButtonHandler, Ctx, FlowContext } from "@spraxium/components";
-import { ContextService } from "@spraxium/components";
-import type { ButtonInteraction } from "discord.js";
-import type { SpraxiumContext } from "@spraxium/components";
-import { FinishButton } from "./finish.button";
+import { ButtonHandler, Ctx, FlowContext } from '@spraxium/components';
+import { ContextService } from '@spraxium/components';
+import type { ButtonInteraction } from 'discord.js';
+import type { SpraxiumContext } from '@spraxium/components';
+import { FinishButton } from './finish.button';
 
 @ButtonHandler(FinishButton)
 export class FinishWizardHandler {
@@ -200,7 +200,7 @@ export class FinishWizardHandler {
     @FlowContext() ctx: SpraxiumContext<unknown>,
   ): Promise<void> {
     await this.context.delete(ctx.id);
-    await interaction.reply({ content: "Setup complete!", ephemeral: true });
+    await interaction.reply({ content: 'Setup complete!', ephemeral: true });
   }
 }
 ```
@@ -255,11 +255,11 @@ The context system uses a pluggable storage adapter configured through the _defi
 </Table>
 
 ```typescript filename="config/components.config.ts"
-import { defineComponents } from "@spraxium/components";
+import { defineComponents } from '@spraxium/components';
 
 export const componentsPlugin = defineComponents({
   context: {
-    storage: "redis",
+    storage: 'redis',
     defaultTtl: 600,
   },
 });
@@ -317,11 +317,11 @@ The default TTL is set in the _defineComponents_ configuration. Individual conte
 The _restrictedTo_ option limits context access to a specific user ID. When set, only interactions from that user ID are dispatched to the handler. Other users who click the component receive the configured _errorMessages.restricted_ message. This is essential for flows where the component is visible to everyone in a channel but should only be actionable by the user who initiated the command.
 
 ```typescript filename="src/commands/verification.command-handler.ts"
-import { Ctx, SlashCommandHandler } from "@spraxium/common";
-import { ContextService, ButtonService } from "@spraxium/components";
-import type { ChatInputCommandInteraction } from "discord.js";
-import { VerifyButton } from "../components/verify.button";
-import { VerificationCommand } from "./verification.command";
+import { Ctx, SlashCommandHandler } from '@spraxium/common';
+import { ContextService, ButtonService } from '@spraxium/components';
+import type { ChatInputCommandInteraction } from 'discord.js';
+import { VerifyButton } from '../components/verify.button';
+import { VerificationCommand } from './verification.command';
 
 @SlashCommandHandler(VerificationCommand)
 export class VerificationCommandHandler {
@@ -339,7 +339,7 @@ export class VerificationCommandHandler {
     const row = this.buttons.rowWithContext(ctx, VerifyButton);
 
     await interaction.reply({
-      content: "Click the button to verify your identity.",
+      content: 'Click the button to verify your identity.',
       components: [row],
     });
   }