I would like to use the BreezeController with Kendo UI Grid, using Kendo's native ODATA support, but it requires that the $callback paramter be supported.

Any time an error message logs or pops referencing a data or object
error, it would be nice that you include in the log the data or object value so we can explore and see what you are getting from us. I belive this is an easy and speedy fix and it will help us a lot. :)

Throughout breeze it is assumed that if an entity has an identity column, that column is part of the primary key. Identity columns do not have to be part of the primary key.

I would like to expose the Name property of any model properties decorated with the DisplayAttribute, so I can use it to display more user friendly messages. This should work automatically with an EF context provider, but should also be available to a custom provider.

The default validation should also look for this value, and use it instead of the field name.

If I navigate to api/breeze/metadata, it returns proper json for my Entity Framework DbContext. However, when called from the app, it just returns Metadata queryfailed, NaN. Would be good to know what is wrong. I have unit tested the context and it is fine. Perhaps a validation screen where you paste in your json and it tells you what is wrong or not supported. thanks.

Allow validators to be added to the EntityManager right away, have EM 'hold' them until MetaData is retrieved, and than add them accordingly. Instead of putting that on the client of EM...

Django and Tastypie expose data in a similar way to ASP Web API. It would be nice to have Breezejs work with Python frameworks.

Use the new json schema to get a controller to return a proper view model instead of what is essentially a domain object.

The idea here is to essentially create a custom provider that connects to a web api that returns view models and when the are returned back. an overridden save changes parses things out and submits them back to EF as domain objects and does whatever needs to be done

Love the project keep it up

It would be most helpful if the results of an Expand could be filtered on the server-side. I.e, if you could have a particular Expand only ever include specific records. This would come in particular use when an institution utilizes "soft deletes", or needs to further filter those expanded records to only include those that should be visible by the current user.

Often (but not always), the parent is the root entity of an aggregate. An Order is the root of an Order aggregate with child line items. When a line item is added/deleted/modified the semantics say that the Order has changed. The concurrency check on the Order governs the entire graph. So we want any line item change to force the Order to be changed. The developer should be able to specify in metadata that the Order changes when anything in its line items collection changes. The specification should be on a navigation path basis. Breeze should respond accordingly

right now breezejs is running on asp.net(as a backend) but since I am a developer of Java Applications that's why I am waiting for the java version of the breezejs

I want to do some stuff inside the ajax adapter, that depends on who initiated the call. For example tracing. In order to do that I need to be able to pass an argument to Breeze that is forwarded to the ajax adapter.

please

Would be great to have an example of breeze exporting metadata for use with knockout validation.

it would be possible to include a function to breeze similar to the included in knockout-validation to translate error messages:

//quick function to override rule messages
ko.validation.localize = function (msgTranslations) {

var msg, rule;

//loop the properties in the object and assign the msg to the rule
for (rule in msgTranslations) {
if (ko.validation.rules.hasOwnProperty(rule)) {
ko.validation.rules[rule].message = msgTranslations[rule];
}
}
};

Related to: http://stackoverflow.com/questions/14316454/translate-breeze-validation-messages

This module would also have access to the user credentials associated with the end user performing the operation to be validated. Ideally, this would be configured via attributes as well as thru a programmatic API.

A tool to create Typescript typed entities from WebAPI metadata in the same way that JaySvcUtil works for JayData

Issued described here: http://stackoverflow.com/questions/14817273/componentone-wijmo-grid-breezejs

One needs to write lots of code to implement query and change interception to EF context. With interceptors we can easily do this with Breeze like WCF Data Services.