mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-25 06:51:11 +00:00
Sebastian Poxhofer
e0cec3dc95
feat(lint): add `types-location` rule and enable it for `lib/modules`
Reviewers consistently ask for exported types to be moved into a
colocated `types.ts`. Add a `renovate/types-location` oxlint rule that
reports `export interface` / `export type` declarations outside such a
file, and turn it on across `lib/modules`.
Re-exports (`export type { X }`, `export type *`), file-local types, and
values (enums, classes, functions) are left alone. `schema.ts` files and
`schema/` directories are excluded via config, matching how
`zod-schema-location` is configured — inferred types belong next to the
schema they are derived from.
Relocating the 87 existing violations means:
- new `types.ts` files for the modules that had none
- `terragrunt/common.ts` folded into its `types.ts`, as it held nothing
else
- `RangeBound` in `versioning/gradle/compare.ts` un-exported, since only
a file-local interface referenced it
- `bazel-module/parser/fragments.ts` split from its inferred types, which
now live in `parser/types.ts` and infer through a namespace import so
each schema keeps its merged name
38 lines
1.1 KiB
TypeScript
38 lines
1.1 KiB
TypeScript
import * as looseVersioning from '../../versioning/loose/index.ts';
|
|
import * as nodeVersioning from '../../versioning/node/index.ts';
|
|
import * as pythonVersioning from '../../versioning/python/index.ts';
|
|
import * as rubyVersioning from '../../versioning/ruby/index.ts';
|
|
import * as semver from '../../versioning/semver/index.ts';
|
|
import type { ToolVersioning } from './types.ts';
|
|
|
|
export const devboxToolVersioning: ToolVersioning = {
|
|
nodejs: {
|
|
api: nodeVersioning.api,
|
|
id: nodeVersioning.id,
|
|
},
|
|
ruby: {
|
|
api: rubyVersioning.api,
|
|
id: rubyVersioning.id,
|
|
},
|
|
python: {
|
|
api: pythonVersioning.api,
|
|
id: pythonVersioning.id,
|
|
},
|
|
// Using loose versioning due to versions like 1.2.3+2
|
|
jdk: {
|
|
api: semver.api,
|
|
id: semver.id,
|
|
},
|
|
// Using loose versioning due to versions like 1.2
|
|
postgresql: {
|
|
api: looseVersioning.api,
|
|
id: looseVersioning.id,
|
|
},
|
|
// Using python versioning due to versions like 1.2beta2
|
|
// seems odd, but Go does actually follow python versioning rules for the language
|
|
go: {
|
|
api: pythonVersioning.api,
|
|
id: pythonVersioning.id,
|
|
},
|
|
};
|