Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improve end-to-end experience of annotating model and flowing thru migrations to schema #5390

Closed
rowanmiller opened this issue May 17, 2016 · 2 comments
Closed

Improve end-to-end experience of annotating model and flowing thru migrations to schema #5390

rowanmiller opened this issue May 17, 2016 · 2 comments
Assignees
@bricelam
Labels
area-test closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed.

Comments

@rowanmiller
Copy link
Contributor

Spun off from #5297 (flowing [Description] into SQL Server extended properties).
@rowanmiller rowanmiller mentioned this issue May 17, 2016
Closed
@rowanmiller rowanmiller added this to the 1.0.1 milestone May 17, 2016
@rowanmiller rowanmiller self-assigned this May 17, 2016
@rowanmiller rowanmiller added area-test and removed pri0 labels Jul 6, 2016
@rowanmiller rowanmiller modified the milestones: 1.2.0, 1.1.0-preview1 Oct 6, 2016
@rowanmiller rowanmiller changed the title Verify end-to-end experience of annotating model and flowing thru migrations to schema Improve end-to-end experience of annotating model and flowing thru migrations to schema Oct 25, 2016
@rowanmiller rowanmiller assigned bricelam and unassigned rowanmiller Oct 25, 2016
@rowanmiller
Copy link
Contributor Author

We need to verify the end to end experience and then look at ways to improve what is generated in migrations (i.e. can providers replace the code that shows what annotations were altered with there own first class methods, etc.).

As part of this, we should consider whether providers play a part in model diffing and if we allow custom migration operations.

@rowanmiller rowanmiller mentioned this issue Oct 25, 2016
Closed
@bricelam
Copy link
Contributor

Possible overlap with #6546

@bricelam bricelam modified the milestones: Backlog, 2.0.0 Jan 12, 2017
@ajcvickers ajcvickers removed this from the Backlog milestone Apr 19, 2018
@ajcvickers ajcvickers added the closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed. label Mar 10, 2022
@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bricelam bricelam

Labels
area-test closed-out-of-scope This is not something that will be fixed/implemented and the issue is closed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@bricelam @ajcvickers @rowanmiller