fix(core): Do not enable strict type validation by default for resource mapper #13037
+144
−54
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.
Summary
In #11837 strict validation was turned on by default for resource mappers, breaking existing workflows that relied on type conversion.
This PR reverts to the old behavior (strict=false) when the resource mapper has no
attemptToConvertTypes
option set.Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-2249/community-issue-sql-data-type-error
fixes #12651
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)