`lint` should allow any value as input

[Stadly]

The lint funciton expects a variable of type Schema as input. As I understand it, if the input is already a Schema it is already a valid JSON Schema, and hence does not need any linting. I think the lint function should take an any or unknown as input. This way the function can be used to check wheter or not an arbitrary value is a valid JSON Schema and hence can be cast to Schema.

The way it is now, in order to check whether a value is a valid JSON Schema, I have to first cast it to Schema. It is better to this cast after running lint, when I know that it is safe.

[somya130104]

Hey! I think lint() would be much more useful if it accepted arbitrary input instead of requiring Schema upfront.

Right now the signature is lint(schema: Schema), but in real usage the value is usually unknown (coming from JSON files / APIs). To call lint, users have to cast first (value as Schema), which kind of defeats the whole point of linting/validation.

My suggestion is to change it to:

lint(schema: unknown): LintResult

Then inside lint, we can simply add a small runtime guard (reject null, strings, numbers, etc. with a proper lint error), and run the existing logic once it’s object-like. This makes lint() usable as the “is this a valid JSON schema?” checker, and users can safely cast to Schema only after it passes.

If you’re okay with it, I can open a PR with the type change, a runtime check, updated docs, and a couple of tests.