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

[Design Goals] Client-side model metadata #6

Open
tonysneed opened this issue Dec 31, 2015 · 2 comments
Open

[Design Goals] Client-side model metadata #6

tonysneed opened this issue Dec 31, 2015 · 2 comments

Comments

@tonysneed
Copy link

Issue for discussing [Design Goals] Client-side model metadata

@weitzhandler
Copy link
Contributor

weitzhandler commented Jul 23, 2017

If my understanding of this issue that we need to base the client-side models based on metadata retrieved from the server, then I agree this will be great.
Especially since we could automate cascaded deletions and other M-0..1 situations, and even validation at some level.

You might be able to re-use EFCore's scaffolding tools to generate client-model or to gather Metadata.
I liked Breeze's way of having a single controller leaving all the work for the cache manager.

Real goal is to have EF and the client side tracker do all the work.

@tonysneed
Copy link
Author

👍

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

No branches or pull requests

2 participants