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.

When you use the skip(n) operation, you are forced to supply and orderBy clause as well or an error occurs. Advisable as it may be to supply one, I suppose you could do without.

A Breeze plugin that pages a query combining remote and cached data in the query results. The paging strategy factors in pending, unsaved changes that could affect sort order (e.g., a name change), exclusion of entities marked for delete, and new entities that qualify for inclusion in the result. Could base it on the DevForce.EntityQueryPager (http://drc.ideablade.com/xwiki/bin/view/Documentation/query-paging)

Add ability to pass functions into where clauses, orderBy clauses, etc., instead of strings, for better intellisense and TypeScript type support.

We have a lot invested in devforce models and the thought of having to maintain multiple models is troubling. I assume it is the saves that are the issue because I'm able to query the df entities without issue.

I don't want to distinguish between local and server data. I'd like the framework to work out the cache state and refresh as necessary based on hints I provide - such as FIFO, LIFO, or callbacks for conflicts.

Described here: http://stackoverflow.com/questions/13796855/autogenerated-keys-for-entities-with-multipart-keys

Please add authentication functionalities as in DevForce.

Ideally, this would be configured via attributes as well as thru a programmatic API.

Support for Indexeddb.

Like the FindEntityGraph method in DevForce (http://drc.ideablade.com/xwiki/bin/view/Documentation/query-working-in-cache), this method would return an array of entities in cache consisting of the root entity and the related entities as specified in the call, perhaps with "expand" syntax. Could use for partial saves as requested in this S.O. post (http://stackoverflow.com/questions/13575058/how-can-i-save-a-single-entity-with-entitymanagers-savechanges-method). Also useful for moving graphs between EntityManagers and to browser local storage.