Fix missed LLM type checking cases: tuple type #1160
Merged
+115
−115
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.
This pull request includes updates to version numbers across multiple
package.json
files and significant refactoring of the validation logic in theTypedBodyProgrammer
,TypedQueryBodyProgrammer
,TypedQueryProgrammer
,TypedQueryRouteProgrammer
, andTypedRouteProgrammer
files.Version Updates:
package.json
files for@nestia/station
,@nestia/core
,@nestia/fetcher
, and@nestia/sdk
to4.4.2
. [1] [2] [3] [4]Refactoring Validation Logic:
LlmValidatePredicator
and replaced its usage with direct checks onprops.context.options.llm
inTypedBodyProgrammer
,TypedQueryBodyProgrammer
,TypedQueryProgrammer
,TypedQueryRouteProgrammer
, andTypedRouteProgrammer
. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]Dependency Updates:
package.json
files to match the new version4.4.2-dev.20241217
. [1] [2]