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.

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

Improvements to reverse engineering (a.k.a. scaffolding a DbContext) for Database First flows #22948

Open
12 of 48 tasks
ajcvickers opened this issue Oct 10, 2020 · 2 comments
Open
12 of 48 tasks
Labels
area-scaffolding composite-issue A grouping of multiple related issues into one issue type-enhancement
Milestone

Comments

@ajcvickers
Copy link
Member

ajcvickers commented Oct 10, 2020

This is a grouping of related issues. Feel free to vote (👍) for this issue to indicate that this is an area that you think we should spend time on, but consider also voting for individual issues for things you consider especially important.


This an "epic" issue for the theme of miscellaneous improvements to reverse engineering (scaffolding) a context from an existing databases/. Specific pieces of work will be tracked by linked issues.

Done in 6.0

Done in 7.0

Done in 8.0

Backlog

@ajcvickers ajcvickers changed the title Miscellaneous improvements to reverse engineering (a.k.a. scaffolding a DbContext) Improvements to reverse engineering (a.k.a. scaffolding a DbContext) Oct 10, 2020
@ajcvickers ajcvickers changed the title Improvements to reverse engineering (a.k.a. scaffolding a DbContext) Improvements to reverse engineering (a.k.a. scaffolding a DbContext) for Database First flows Oct 10, 2020
@ajcvickers ajcvickers added this to the Epics milestone Oct 11, 2020
@w3rm
Copy link

w3rm commented Jan 20, 2022

I will be very happy with this one -> Revisit navigation naming convention when reverse-engineering composite keys #16711

@AraHaan
Copy link
Member

AraHaan commented Mar 24, 2022

I will be happy with this one -> SP's being scaffolded even if it requires them being done at the template level.

However if I was to implement it myself, how could the parameters, it's name, etc be known by the template system, or even it's implementation?

I guess this is something that merits a source dive into ef6 to find out.

@ajcvickers ajcvickers added the composite-issue A grouping of multiple related issues into one issue label Dec 6, 2022
@ajcvickers ajcvickers modified the milestones: Epics, Backlog Dec 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-scaffolding composite-issue A grouping of multiple related issues into one issue type-enhancement
Projects
None yet
Development

No branches or pull requests

5 participants