feat(hono): add orverride.hono.validatorOutputPath option

[soartec-lab]

Status

READY

Description

Until now, validator.ts was output to the same directory as other files output to target.
In fact, validator.ts is only referenced in handlers, so I want to output it to the same hierarchy instead of target.
So I added an option to give me control over it.

Before:

src/
├── endpoints.context.ts
├── endpoints.ts
├── endpoints.validator.ts  <--- They are grouped under `target`
├── endpoints.zod.ts
└── handlers

After:

src/
├── endpoints.context.ts
├── endpoints.ts
├── endpoints.zod.ts
└── handlers
    ├── createPets.ts
    ├── deletePetById.ts
    ├── healthCheck.ts
    ├── listPets.ts
    ├── schemas
    ├── showPetById.ts
    └── validator.ts  <--- By specifying the path, output will be under handlers.

Related PRs

None

Todos

The hono client hasn't yet been tests and docs, so I will add those in a separate PR.

• Tests
• Documentation
• Changelog Entry (unreleased)

Steps to Test or Reproduce

export default defineConfig({
  petstoreSplitValidatorOutputPath: {
    input: '../specifications/petstore.yaml',
    output: {
      target: '../generated/hono/petstore-split-validator-output-path/endpoints.ts',
      schemas: '../generated/hono/petstore-split-validator-output-path/handlers/schemas',
      mode: 'split',
      client: 'hono',
      override: {
        hono: {
          handlers: '../generated/hono/petstore-split-validator-output-path/handlers',
          validatorOutputPath: '../generated/hono/petstore-split-validator-output-path/handlers/validator.ts',
        },
      },
    },
  },
});

[soartec-lab]

I'll merge it.