-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Model snapshot is used without type mappings #16239
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
Comments
ajcvickers
added a commit
that referenced
this issue
Jun 25, 2019
Initial fix for #16239 Required to unblock dotnet/aspnetcore#11531 (comment)
ajcvickers
added a commit
that referenced
this issue
Jun 25, 2019
Initial fix for #16239 Required to unblock dotnet/aspnetcore#11531 (comment)
ajcvickers
added a commit
that referenced
this issue
Jun 25, 2019
Initial fix for #16239 Required to unblock dotnet/aspnetcore#11531 (comment)
ajcvickers
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Jul 6, 2019
ajcvickers
added a commit
that referenced
this issue
Jul 6, 2019
Fixes #16239 Fixes #12212 Also, make the SnapshotModelProcessor finalize the model. I investigated whether it would be better to only store this sometimes, but that then still requires making some assumptions (basically using some conventions and/or the type mapper doing what it does in conventions) when loading the snapshot to ensure we find the right type for the provider being used. Storing it always is clean and simple, decouples from conventions when loading, and means we don't have to do special magic for facets that come from value converters.
ajcvickers
added a commit
that referenced
this issue
Jul 7, 2019
Fixes #16239 Fixes #12212 Also, make the SnapshotModelProcessor finalize the model. I investigated whether it would be better to only store this sometimes, but that then still requires making some assumptions (basically using some conventions and/or the type mapper doing what it does in conventions) when loading the snapshot to ensure we find the right type for the provider being used. Storing it always is clean and simple, decouples from conventions when loading, and means we don't have to do special magic for facets that come from value converters.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
This caused an issue with SQLite snapshots--see dotnet/aspnetcore#11531 (comment)
There is an easy fix to revert the break, but we may need the model snapshot to actually construct type mappings. See also #14000
The text was updated successfully, but these errors were encountered: