Skip to content

Same Naming & Eslint comment #2459

@metinsut

Description

@metinsut
export type InitialStepRequestStepKind =
  (typeof InitialStepRequestStepKind)[keyof typeof InitialStepRequestStepKind];

// eslint-disable-next-line @typescript-eslint/no-redeclare
export const InitialStepRequestStepKind = {
  FORM: "FORM",
  CORE_ACTION: "CORE_ACTION",
  MANUAL: "MANUAL",
  OFFER: "OFFER",
  ONBOARDING: "ONBOARDING",
} as const;

I’m using Biome instead of ESLint, so the generated code shouldn’t include any ESLint-specific comments.
Also, having both the type and const share the same name causes import conflicts — they should be named differently or made configurable.

  coreApi: {
    input: "...",
    output: {
      mode: "tags-split",
      target: "./clients",
      schemas: "./schemas",
      client: "axios",
      workspace: "./core",
      indexFiles: true,
      biome: true,
      override: {
        header: false,
        useTypeOverInterfaces: true,
        suppressReadonlyModifier: true,
        mutator: {
          path: "./custom-instance.ts",
          name: "customInstanceCore",
        },
      },
      clean: true,
    },
    hooks: {
      afterAllFilesWrite: ["bun run lint:unsafe"],
    },
  },

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions