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

Make model namespace consistent #438

Closed
chinadragon0515 opened this Issue Jun 13, 2016 · 2 comments

Comments

Projects
None yet
1 participant
@chinadragon0515
Contributor

chinadragon0515 commented Jun 13, 2016

Now, when user wants to extend a model based on model builder from EF, he needs to use low level ODL lib code to extend the model, we want to make it easier, make ODataConversionModelBuilder accept an existing model, tracked with issue OData/WebApi#755

Also when user wants to add some new entity type and entity set, and these entityset and type are used by operation, the model extend will need to overwride some existing logic.

Need to make this part model simpler.

@chinadragon0515

This comment has been minimized.

Contributor

chinadragon0515 commented Jun 14, 2016

Fix namespace issue too, container will use "default" as namespace.

@chinadragon0515 chinadragon0515 changed the title from Make model extend more easier to Make model extend more easier and namespace consistent Jun 20, 2016

@chinadragon0515 chinadragon0515 added docs and removed ready labels Jun 22, 2016

@chinadragon0515 chinadragon0515 changed the title from Make model extend more easier and namespace consistent to Make model namespace consistent Jul 1, 2016

@chinadragon0515

This comment has been minimized.

Contributor

chinadragon0515 commented Jul 5, 2016

code merged. close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment