fix for having a proper json schema for "where" #11027
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Enhancement: Added proper support for
where
filter JSON schema in LoopBack to reflect all documented operators (e.g.,eq
,neq
,gt
,gte
,inq
,like
,regexp
, etc.) and logical clauses (and
,or
,not
,nor
), based on the [official LB4 filter documentation](https://loopback.io/doc/en/lb4/Where-filter.html#operators).This improves the output of
getWhereJsonSchemaFor()
to generate accurate OpenAPI schemas and improves downstream schema validation/generation (e.g., for clients or Zod-based tools).Checklist
npm test
passes on your machinepackages/cli
were updatedexamples/*
were updated