Skip to content

fix: tolerate EF value objects#6

Draft
dkattan wants to merge 2 commits into
fix/ef-single-key-metadatafrom
fix/owned-complex-tolerance
Draft

fix: tolerate EF value objects#6
dkattan wants to merge 2 commits into
fix/ef-single-key-metadatafrom
fix/owned-complex-tolerance

Conversation

@dkattan

@dkattan dkattan commented May 11, 2026

Copy link
Copy Markdown

Summary

  • expose the next required Coalesce dependency slice for the Immybot response-harvest stack

Docs

  • Contributor docs impact: this is an internal tolerance fix for owned/complex EF types; no separate public docs page is needed beyond the stack note.

dkattan and others added 2 commits May 11, 2026 13:28
Use EF metadata during validation so owned, complex, and converted properties don't get treated like navigations.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@dkattan dkattan force-pushed the fix/ef-single-key-metadata branch from e54d745 to 047c517 Compare May 11, 2026 18:33
@dkattan dkattan force-pushed the fix/owned-complex-tolerance branch from 823866d to c799006 Compare May 11, 2026 18:33
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.

1 participant