Skip to content

fix(server): prefer write-clause type in extract_crud_info, bump to 1.4.3 (#121)#122

Merged
ds1sqe merged 1 commit into
masterfrom
develop
Apr 6, 2026
Merged

fix(server): prefer write-clause type in extract_crud_info, bump to 1.4.3 (#121)#122
ds1sqe merged 1 commit into
masterfrom
develop

Conversation

@ds1sqe
Copy link
Copy Markdown
Owner

@ds1sqe ds1sqe commented Apr 6, 2026

For Match + Insert/Put queries, extract_crud_info() was reporting the first matched entity as type_name instead of the actual write target. Separate match-clause type info into fallback variables so the Insert/Put statement always takes priority.

Also refactor validation.rs match arms to use idiomatic match guards.

….4.3 (#121)

For Match + Insert/Put queries, extract_crud_info() was reporting the
first matched entity as type_name instead of the actual write target.
Separate match-clause type info into fallback variables so the
Insert/Put statement always takes priority.

Also refactor validation.rs match arms to use idiomatic match guards.
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 6, 2026

Codecov Report

❌ Patch coverage is 95.23810% with 1 line in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
type-bridge-core/crates/core/src/validation.rs 75.00% 0 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

@ds1sqe ds1sqe merged commit 318c5a9 into master Apr 6, 2026
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

extract_crud_info() reports the first matched entity instead of the written relation for Match + Put/Insert(Relation) queries

1 participant