How can we improve Breeze.js?

EntityManager should accept different service address for generating metadata

Currently EntityManager accepts a service name, which it uses to fetch metadata and also resolve controller/actions.
E.g.
var manager = new breeze.EntityManager("servicename");

At the Web Api end, I will have multiple controllers. E.g. OrderController, CustomerController etc... based on the need of my application. I will also have a HomeController where I will have the method Metadata() that is used by Breeze to fetch metadata.

When I try to make my first query, Breeze automatically tries to fetch the metadata information. So in this example it will hit the following URI: http://servicename/metadata, but ideally it should be hitting http://servicename/home/metadata.

There is no way to set the metadata URI/Servicename in EntityManger Api, which is required.

I cannot set the service name to "servicename/home" while creating EntityManager because that will cause a problem when I want to hit another controller. E.g. http://servicename/order.

Currently the only workaround is to manipulate the route at server end using the GlobalConfiguration. But I feel it is not a clean way of doing this. EntityManager Api should have a property like MetadataAddress.

Thank you.

19 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
DotnetCoE shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base