#827 fix boolpredicate validation

[walker-sean]

Closes #827

• OpenAPIBackend constructor fixed to properly assign the validate option as a member.
• Also renamed BoolPredicate to the more precise, less redundant ContextPredicate
• Added tests to verify use of predicates as validate value

[Copilot]

Pull request overview

Fixes issue #827 where supplying a predicate function for OpenAPIBackend’s validate option was being coerced to true, preventing conditional validation from working.

Changes:

• Rename BoolPredicate to ContextPredicate and update the validate option/member types accordingly.
• Fix OpenAPIBackend constructor to preserve the validate option value (boolean or predicate) instead of coercing it.
• Add tests covering predicate-based validation behavior (skip vs run validation).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/backend.ts	Updates predicate type name and fixes validate assignment to avoid boolean coercion.
src/backend.test.ts	Adds regression tests ensuring validate predicates are invoked and affect validation flow.

Comments suppressed due to low confidence (1)

src/backend.ts:75

• Renaming the exported BoolPredicate type to ContextPredicate is a breaking public API change for TypeScript consumers (they may import BoolPredicate today), but the package version is still on the v5 minor line. Consider keeping a backward-compatible alias export (e.g. export type BoolPredicate = ContextPredicate with a @deprecated tag) so existing imports keep compiling while still steering users to the new name.

export type HandlerMap = { [operationId: string]: Handler | undefined };

export type ContextPredicate = (context: Context, ...args: any[]) => boolean;

/**
 * The different possibilities for set matching.
 *
 * @enum {string}

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.