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. Navigation property mapping issue with changed foreign key

    To reproduce:


    1. Have an entity with a navigation property and associated foreign key.

    2. Set the foreign key value.

    3. Execute a query for the entity belonging to that foreign key value.

    4. Set the foreign key to a different value.

    5. When the query in (3) finishes executing, it sees that there is a mapping in the unattached children map and sets the navigation property on the entity. Therefore changing the foreign key back to the value set in (2) and we lose the value set in (4).

    3 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 →
  2. Breeze/OData calling FetchEntityByKey should not use filter syntax

    When using Breeze with OData and calling the entityManager.FetchEntityByKey() the following request is sent:

    /odata/Customers?$filter=Id eq 2

    I would have expected

    /odata/Customers(2)

    for more see: http://stackoverflow.com/questions/20440358/breeze-odata-calling-fetchentitybykey-does-use-filter-entitysetcontroller-geten

    4 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 →
  3. Fire event on metadata load

    We could use an event indicating that the MetadataStore is loaded. As discussed in stackoverflow http://stackoverflow.com/questions/14146841/how-to-attach-to-metadataloaded-event-or-equivalent-in-breeze-js/20470781#20470781 I see that the recommended solution is to call fetchMetadata. But, we have experienced – more than a little – that sometimes fetchMetadata fails, but subsequent queries succeed. Preventing queries while retrying fetchMetadata would be a lot of work. With an event, we could very easily handle metadata initialization – in our case validations.

    14 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 →
  4. OData Version 4.0 Support

    Support for OData version 4.0, when it is finalized. This will allow filtering by derived complex types, among other things.

    http://www.odata.org/documentation/odata-version-4-0/

    The above mentioned feature I'd like to see available with breeze:
    http://docs.oasis-open.org/odata/odata/v4.0/cs01/part2-url-conventions/odata-v4.0-cs01-part2-url-conventions.html#_Toc365046429

    243 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 →
  5. Also support Almond for AMD

    I use Almond (https://github.com/jrburke/almond) as a (smaller) replacement for RequireJS, but have some trouble getting Breeze to work with it.

    Main issue is that Almond doesn't allow anonymous modules, which is how Breeze defines itself at the moment.

    12 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 →
  6. Access EntityManager from Node.JS as server side data access API

    I'm interested in being able to use the Breeze.js EntityManager and query capabilities within a node console service to access a remote Data Service that exposes an BreezeJS/OData compliant RESTful endpoint.

    We currently have a Data Service implemented using Node.js, MongoDB and the Breeze.js breeze-mongodb module.

    We have web browser hosted clients that access the MondgoDB using the Breeze.js client API (EntityManager) and the Data Service described above.

    I need to create another Node.js service that can access the same MongoDB database that the web browser hosted clients do, and for consistency/simplicity I would like to use the same data…

    51 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 →
  7. Create an example for RhoMobile

    Create a test example using the RboMobile platform.

    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 →
  8. 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 →
  9. Fix mobile site navigation

    Entire nav is at top of each page, clicking link looks like page didnt load

    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 →
  10. Entity creation: Initialise Foreign Key - Properties which are Nullable with Null (Currently it's 0)

    i'm currently working on a angular/breeze/web api - based solution.
    to simplify user input i'm marking all the required fields thanks to the getValidationErrors() method. in this case the user presses an add button on a grid, then a new entity gets created and angular takes care of the rest. sounds good right?
    This works for regular Properties but not for Foreign Keys because they get created with an "0" Value (I didn't assign defaults and the column is not nullable) and therefore validationErrors is empty after entity creation which is imho wrong.

    additional information:
    http://stackoverflow.com/questions/20339402/breeze-entity-creation-foreign-key-column-is-set-to-0-by-default

    19 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 →
  11. Overload for Validator.register so i can register multiple Validators in one shot

            Validator.register(requireReferenceValidator);
    
    Validator.register(twitterValidator);

    instead, just pass an array

    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 →
  12. Using breeze (odata) in full duplex communication (websockets)

    Hey, I will not pretend to be an expert of breeze, but I like the concept and all the work you have done!
    I'm thinking of developing a proof of concept where I use breeze to communicate over websockets instead of http...

    Has anyone done this with breeze? Am I a complete moron? Should I go bananas on this?

    8 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 →
  13. EntityManager should accept different service address for generating metadata

    Currently EntityManager accepts a service name, which it uses to fetch metadata and also resolve controller/actions.
    E.g.
    var manager = new breeze.EntityManager("servicename");

    At the Web Api end, I will have multiple controllers. E.g. OrderController, CustomerController etc... based on the need of my application. I will also have a HomeController where I will have the method Metadata() that is used by Breeze to fetch metadata.

    When I try to make my first query, Breeze automatically tries to fetch the metadata information. So in this example it will hit the following URI: http://servicename/metadata, but ideally it should be hitting http://servicename/home/metadata.

    19 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 →
  14. Add KeepDetached merge strategy

    Please allow the scenario when entities which aren't saved in the database yet can be returned from the server.

    My scenario is:
    1. There is a grid which is bound to the order items. The grid is used for displaying order items for a new or already saved order.
    2. There is a sever method which constructs new order with order items. The order and order items are new entities and aren't saved in the DB yet.
    3. I would like to display data in the grid and add the order to the EntityManager and save if user is ok…

    3 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 →
  15. unnecessarily complex eample in an otherwise well done explaination

    //I believe the following source structure offers better pedagogy
    //Note the use of 'metaStore' vs simply 'store' and the avoidance of excessive convenience variables.
    //Also, there is a clearly defined collection of entities suitable for a JSON file, in fact!

    'use strict';

    // Creates a metadataStore with 3 Northwind EntityTypes:
    // Product, Category, Supplier and a Location ComplexType
    function createMetadataStore(serviceName) {

    // Convenience variables
    var DT = breeze.DataType;
    var Identity = breeze.AutoGeneratedKeyType.Identity;

    var serviceName = 'api'; // root path for data from the server
    var defaultModelNamespace = 'UE.Models';

    //meta data definitions
    var CategoryType = {

      // Header info
    
    shortName: "Category",
    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 →
  16. filters need to be put in request body, not uri

    I have a very large table with about two dozen possible different filtering fields to narrow down what is sent to the client on what I call a search page. I made a "Search" method using POST in the web api controller with the idea that I would put the filters in the request body, since I think all of them are too much for a URI. Can Breeze handle that?

    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 →
  17. Not always best to filter and sort on the client.

    I am going through this tutorial and saw the statement: "Aside from granting the client more flexibility for free, this approach also performs much better. The client-specified filtering, ordering, paging, and expand will execute on the data tier, not on the server tier.".

    I am working on porting applications that may contain thousands, if not millions, of records in a table. I know from experience that filtering, ordering and paging of such large tables need to be done on the database server before being sent anywhere else, or performance goes through the floor. I also have used stored procedures with…

    1 vote
    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 →
  18. Tutorial: how to use Breeze with AngularJS, my own WebAPI, no database, no Azure.

    Write a tutorial on how to use Breeze with AngularJS, my own WebAPI, no database access, no Azure.

    2 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 →
  19. use serverside model default values on entity creation clientside

    hi there
    i would like to use default values from the database model on the clientside. when i retrieve the metainformation a property deaultValue is already there but it doesn't get refelcted when using manager.createEntity(...)
    http://stackoverflow.com/questions/16741155/how-does-breeze-handle-database-column-defaults

    4 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 →
  20. Please make the Breeze api available for Java servers as well like Tomcat

    Normally I saw all the examples in ASP.net as the Backend server, can we expect that Breezejs will come for Java backend as well

    6 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 →
1 2 5 7 9 13 14
  • Don't see your idea?

1. BreezeJS Feature Suggestions

Categories

Feedback and Knowledge Base