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.
-
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 "First_Name", "Last_Name", 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?