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.

  1. Support NHibernate

    Support NHibernate out of the box like EF

    174 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. 48 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 53 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support for PHP and MySQL

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

    404 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    0.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.

  7. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Named save

    Route a save request to a different save method on the server (on the controller).

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    Breeze 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).

    http://www.breezejs.com/documentation/download

  10. Support for query parameters

    Something like

        var query = new EntityQuery()
    
    .from("CustomersStartingWith");
    query.parameters.add("A");

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Build 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”);
  11. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Attributes on controller actions to block the use of Select and Expand

    Define attributes that block the use of Select and Expand.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    Attributes 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.

  13. 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 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. 48 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. 233 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  Flag idea as inappropriate…  ·  Admin →
1 2 4 Next →
  • Don't see your idea?

1. BreezeJS Feature Suggestions

Categories

Feedback and Knowledge Base