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.
-
Add client NuGet packages
Add a NuGet package which installs the scripts necessary for a breeze client app.
3 votes -
Angularjs support
I'm curious as to what you guys are cooking up for Angular...It seems like it could in theory be pretty easy as angular binds to plain objects, but I'm sure there are plenty of wrinkles. Glad we have brilliant minds such as yourselves to figure this stuff out!
Just off the top of my head I'm thinking in the query promise callback you could set the array to what forEach is observing via an angular.apply() call, since we're outside of angular. Or better yet somehow integrate the promise with forEach since this is what angular uses if I remember correctly.…34 votes0.74.2 includes a new Todo sample (Todo-Angular) that demonstrates Angular at work with Breeze. The new sample is an “almost” exact copy of the “knockout” Todo sample and we’ll be documenting it like the original within the next few days.
-
I can use asp.net web api with other object then EF.
In web api how i can use other objects not only EF.
3 votes -
Support $inlinecount in queries
The OData 2.0 spec describes the $inlinecount parameter (http://www.odata.org/documentation/uri-conventions#InlinecountSystemQueryOption) as a way to include with query results the count of all records that satisfy the filter clause without respect to the paging parameters (top and skip) that may be in the query request.
36 votes0.75.1 is now live, and adds an ’inlineCount" method to the EntityQuery.
This provides support for providing, in addition to standard query results, the count of records that would be returned by this query if no ‘skip’ or ‘take’ option were included on the query.
In other words, the count is calculated after applying any filters/where clauses but before any skip/take operations.
See the API Docs for more details. Both OData and WebApi endpoints are supported with this feature.
-
3 votes
TimeSpan support added in build 0.84.1.
-
Correct the instructions on this page
EFContextProvider constructor has been updated to not need the "dbconnectionname" - the instructions still have that.
SaveChanges() has changed to use JObject, so change it from JArray
4 votesSorry for the delay V K.
The corrections are now live.
-
Mocking Data Calls
Allow for Breeze's data service calls to be able to be overridden with mock data calls, so data can be seen without needs to make actual ajax calls for designing and testing. Similar to amplify's model and using mockJSON with it.
35 votesAs of version 0.70.1, Breeze supports the ability to completely customize or replace any Ajax communication between the Breeze client and the web service on the server.
The Breeze documentation on our Ajax support is still in progress, but hopefully the following will get you started:
-
Named save
Route a save request to a different save method on the server (on the controller).
23 votesBreeze 1.3 adds named saves.
By default the EntityManager.saveChanges method sends a save request to an endpoint called “SaveChanges”. With “Named Save”, you can target a different server endpoint such as an arbitrarily named action method on another Web API controller. There are two new properties on the SaveOptions class. A resourceName (for the action method) and a dataService (for targeting a different controller).
-
Attributes on controller actions to block the use of Select and Expand
Define attributes that block the use of Select and Expand.
13 votesAttributes for blocking Select and Expand were added a few builds ago, but we’re marking it complete on UserVoice today. Sorry for the delay.
Breeze 1.3.1 is now available, including Inheritance and OData writes/saves.
-
Attribute on controller actions to limit result size
Add an attribute that can be placed on a Web API controller action to limit the number of entities that can be returned in this query.
13 votesThis was updated in the Breeze source a few builds ago, but we missed updating it here.
We now support this attribute for MVC4 WebApi services: http://msdn.microsoft.com/en-us/library/system.web.http.resultlimitattribute%28v=vs.108%29.aspx
-
Support for query parameters
Something like
var query = new EntityQuery()
.from("CustomersStartingWith");
query.parameters.add("A");10 votesBuild 0.76.2 adds a new EntityQuery method: withParameters.
This method allows custom parameters to be passed to any server side method, in addition to those that Breeze uses for its normal querying. Custom parameters can be mixed in with other query clauses.
For example:
var query = EntityQuery.from(“EmployeesFilteredByCountryAndBirthdate”) .withParameters({ BirthDate: “1/1/1960”, Country: “USA” }) .where(“LastName”, “startsWith”, “S”) .orderBy(“BirthDate”); -
camelCase translation option for entity properties defined as PascalCase on server
Look at the case of the first letter of bound property and behave differently if upper case
4 votes -
Naming convention for mapping metadata names
A mapper should accept filters that can do the mapping automatically. CamelCasing is one such filter. Another might do something nice with stuff like "FirstName", "LastName", etc.
1 voteCompleted and deployed. We still need to document it.
-
Metadata name mapper for the client
Add a mapping mechanism in the metadata on the client that lets us have the names we want.
1 voteCompleted and deployed. We still need to document it.
-
233 votes
Inheritance is 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.
-
48 votes
- Don't see your idea?