1. BreezeJS Feature Suggestions
Help us make Breeze.js better by letting us know what you’d like to see next.
Suggest new features, vote on existing ones, or fork Breeze in GitHub and send us a pull request.
78 results found
-
Support executing arbitrary stored procedures within the transaction scope SaveChanges
Support executing arbitrary stored procedures within the transaction scope SaveChanges
[Or] allow some way of tying in to the transaction scope for any SQL
26 votesComplete as of the 1.4 release.
Please refer to the release notes and associated documents for the full details.
-
Seperate out EFContextProvider
I would like to start out by saying nice job on breeze. You guys have a breeze mvc webapi dll for those people doing .net. I really like the EFContextProvider, but I think it would be cool if it was a seperate project. This would allow users to use it in different class libraries to create repositories and a unit of work for the different models that you create and have one place to manage it. Keep it breezy, thanks
141 votesCompleted in Breeze 1.4.2.
-
"Finding entities in the cache" section appears twice in the "EntityManager" documentation page
"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!
1 voteCorrected the typo and pushed the change live.
Thanks Tommi!
-
Add a closing bracket
There is a closing bracket missing on this page:
http://www.breezejs.com/documentation/customizing-ajaxLine 7 in the second code block:
if (isFooRequest(xhr))It's no big deal but thought I'd let you know...
4 votesThanks Ben.
I just corrected this typo and pushed the revision live.
Thanks again,
John
-
why the change in BreezeWebApiConfig?
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.
1 voteRelease notes have been updated (and pasted to this UserVoice request).
-
Examples that uses other backends.
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..
219 votesChanging status to complete.
Our NodeJS/MongoDB sample was added in 1.4.0, and our Ruby sample went live shortly before 1.4.2.
________Work is well underway on a Java backend for Breeze, using Hibernate and JAX-RS. Please check out https://github.com/Breeze/breeze.server.java/tree/master/breezejs-hibernate .
The NorthBreeze sample (https://github.com/Breeze/breeze.js.samples/tree/master/java/NorthBreeze ) is a web application that uses the breezejs-hibernate library.
-
Make your site look better of the iPhone
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.
1 voteThanks anon.
I’ve updated the Live Tutorial block so you shouldn’t have a problem with it anymore.
Can you provide more info on the Feedback issue? Admittedly I’m on Android 4.2.2, so don’t share your iPhone experience, but any info you can provide would be helpful.
You can reach me at johnl@ideablade.com.
Thanks,
John
-
Make breeze play nice with AMD loaders like require.js
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.37 votes1.2.4 removed internal dependencies on RequireJS. External dependencies on RequireJS should now play nice with Breeze.
-
update the sample code for a Custom EFContextProvider
the two overridden methods should be protected, not public. I noticed when extending within my project. Great library. Thanks!
1 voteThanks for the clarification.
I’ve updated the docs so the override and virtual are all protected now (as they should be).
http://www.breezejs.com/documentation/custom-efcontextprovider
Thanks for catching this.
-
Expose the 'name' property on the Validator class
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.
1 voteRichard,
This has been completed as of build 1.2.7 (now available).
The API has been updated here:
http://www.breezejs.com/sites/all/apidocs/classes/Validator.html#property_name
-
Update SaveChangesCore to allow custom validation errors to be returned
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.
3 votesFixed in the 1.0 release.
-
Support for MongoDb out of the box like EF
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.
84 votesComplete as of 1.4.
Docs are available here:
http://www.breezejs.com/documentation/mongodb
And the new Zza! (Node/MongoDB) sample can be found here:
-
Support for PHP and MySQL
Support a PHP connector for MySQL. This is one of the most often used data connections.
404 votesPointed to the sample on our website
-
Support NHibernate
Support NHibernate out of the box like EF
174 votesRequest completed in the 1.4.2 release.
-
Support the .NET DateTimeOffset type
The DateTimeOffset CLR type is a struct, mainly composed by a DateTime struct and a TimeSpan struct (the latter expressing time zone offset).
In SQL Server 2008 and above, there is also a corresponding "datetimeoffset" native SQL server type that maps nicely with EF.The idea of this data type is to be able to represent a date/time, but also a specific time zone.
Note! The DateTime type is sufficient to calculate exact universal times (by always practicing dates stored as UTC etc.), but it has no information about the time zone e.g. of the user that modified some object.
…
1 voteCompleted as of Breeze 1.1.1.
See http://www.breezejs.com/documentation/download for more information.
-
Full oData CRUD support
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
104 votesOData Saves are now available in Breeze 1.3.1.
We’re labeling this feature as beta for now, not because we expect the APIs to change in the future, but because we still only have a reasonably small set of test scenarios and need your feedback to determine if we’ve missed any important test cases.
-
Try to coerce string bindings to a data property's data type
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.
11 votesAs of Breeze 0.80.2, automatic datatype coercion is now applied when setting any Breeze ‘entity’ properties.
This means, for example, that when setting a string to a numeric or date field that Breeze will attempt to coerce the value to the correct datatype before assignment.
-
We should now only see customers with company names that start with "C" that are also in cities whose names contain "er".
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.
1 voteGreat catch. Thank you!
I’ve updated it in the source on GitHub and we’ll be pushing the change live with the next push of the Tutorial.
Thanks again,
John
-
Strong Name the Breeze.WebApi.dll
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.
2 votes -
48 votes
- Don't see your idea?