"Finding entities in the cache" section appears twice in the "EntityManager" documentation page.

Please remove one of the duplicates.

Page Url: http://www.breezejs.com/documentation/entitymanager-and-caching

Best regards!

There is a closing bracket missing on this page:
http://www.breezejs.com/documentation/customizing-ajax

Line 7 in the second code block:
if (isFooRequest(xhr))

It's no big deal but thought I'd let you know...

I just upgraded from 1.3.0 to 1.3.1 and there appears to be a change in the Routing Template from "api/{controller}/{action}" to "breeze/{controller}/{action}". This caused some confusion as it broke my application as the route was changed. Once I found the issue it was fine but there was nothing in the release notes that explained that there was a change. As I used the default routing that came with the nuget package BreezeWebApiConfig.cs got updated automatically which caused the issue. In future please include routing changes into the release notes.

You know that many developers have already loved Breeze.js but that's not it. It has the potential to be a really great technology for the new breeds of developers (beginners)...

I'd like to suggest to include examples on how Breeze.js works with other backend technologies such as Java, PHP, etc..

Touting your mobile chops sets the bar a little higher than you've hit on an iPhone in portrait orientation. The "feedback" button covers code and there's a section that may read "live tutorial" but I'm not sure as it's not legible.

There is a problem when you want to AMD load breeze.js (see http://stackoverflow.com/questions/13937539/breezejs-and-requirejs-not-working-as-expected)
I think the only problem is that breeze.js should define dependencies in the define() call. Currently it calls define(), but doesn't pass ['ko', 'Q'] as dependencies, but instead looks for ko and Q in the global namespace.
If this is too much trouble, please provide second breeze-amd.js version.

the two overridden methods should be protected, not public. I noticed when extending within my project. Great library. Thanks!

Currently, you can initialize a new Validator object with a name in the constructor, but once it's created you can't get at the name through any public property. Exposing a new 'name' property on the Validator Class would let you easily scan the list of ValidationErrors for broken rules associated with a custom validator name.

Adding Custom Validation Attributes (e.g. "[MyCustomAttribute]") to your model class causes the SaveChangesCore() method to throw an 'ArgumentNullException' instead of the expected 'ValidationException' when the model Custom Validation Attribute is invalid. This is because the exception message formatting code assumes that 'key.EntityKeyValues' will never be null, which apparently is not the case when a Custom Validator prevents the model from being saved. It would be nice to correct the code to assume 'key.EntityKeyValues' can be null so that the server-side validation exception message can at least be returned to the client. See http://stackoverflow.com/questions/14332833/breeze-js-not-returning-custom-validation-error-messages-from-server for more details.

I would like support for other popular noSql databases like MongoDB and RavenDB. If this can already be supported then just some proper documentation on how it can be achieved and some supporting example projects would be very helpful. Thanks.

Support a PHP connector for MySQL. This is one of the most often used data connections.

Support NHibernate out of the box like EF

per this forum reply, full crud support for odata services is not currently supported in breeze.

http://www.ideablade.com/forum/forum_posts.asp?TID=3793&PID=15186#15186

Knockout binding of textbox to an integer data property can be fail validation because it sets the property with a string. Breeze, which knows the property's datatype, should attempt to parse the string to that datatype. Extend this idea to all datatypes (including date) and for all model libraries.

Step 5 of 6 in tutorial:
We should now only see customers with company names that start with "C" that are also in cities whose names contain "er".

Change C to S.

Can you please apply a strong name to the DLL within the NuGet package. This woudl save having to manually apply it for every update.

Described Here: http://stackoverflow.com/questions/13982046/ef-entity-with-timespan-property-not-supported-in-breeze-js