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. Please provide more tutorials like knockout js such that the user can understand a bit more. Thanks

    Please provide more tutorials like knockout js such that the user can understand a bit more. Thanks

    26 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. Automatically remove from cache items that were deleted by someone else if an Expand clause did not return it

    When multiple users play with similar data and one of the navigation property (to a list of children for example) has hard deletable items, it is possible for one user to load all the children in cache, then for another to delete those children. Then, for user 1, even if he refetches the parent objects with an expand clause to the children, Breeze will currently reattach even those children that were not returned from the server - the deleted ones. There is no easy way currently out of manually clearing the cache or querying directly for each child to check…

    30 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. Switch to Bluebird promises

    Bluebird promises are orders of magnitude faster than Q promises, they're more modern and they provide a more consistent API for now.

    Switching to them should show improvements in speed as well as debuggability (better long stack traces for example).

    17 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. Documentation Error: ComplexAspect class has no entityAspect property

    Instead there is a method "getEntityAspect()"

    2 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 →

    This is not an error.

    Breeze ‘complex objects’ have a ‘complexAspect’ property that is analogous to the ‘entityAspect’ that is found on ‘entities’.

    All complex objects ALSO have a GetEntityAspect() method. The GetEntityAspect method returns the top level EntityAspect associated with the complexObject ( complex objects can be nested so this may go thru multiple parent objects before returning the final parent EntityAspect – this is why this is a method and not a property).

    Entity objects by comparision have only a single entityAspect property.

  5. 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 →
  6. Title of the page doesn't update in docs

    On Linux Mint 16, Chrome v.31.0.1650.63

    Jumping around different doc pages like MetadataStore to EntityManager to ... doesn't change what I see in the Chrome tab title area.

    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 →
  7. More node.js / mongodb love

    I fall in love with Breeze, but the support in node / mongodb still needs a lot of work. I can't live with breeze anymore but I can't support .NET.

    I saw the TODO but wasn't updated since August 2013.

    Things like associations would change it completely.

    I vote for some sweet love for those who don't use .NET

    45 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. TypeScript breeze.d.ts: ValidatorFunction should return boolean

    The current breeze.d.ts file says:

    interface ValidatorFunction {
    (value: any, context: ValidatorFunctionContext): void;
    }

    Since a value can be either valid or invalid (true or false) in my opinion this should be a function returning a boolean. Also, the context parameter in the Validator constructor can be empty so it would be better if "context" is an optional parameter.
    And: the "message" part of the ValidatorFunctionContext is declared as "string" but can be a function also and "any" would be correct.

    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. Make the e-mail validator to accept capital letters

    The built in email validator does not accept capital letters , so I have made custom validator to do so.

    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 →
  10. Add method "SaveChanges" on EntityAspect

    It would be nice if there is a method "SaveChanges" directly on the EntityAspect, similar to "RejectChanges". This makes it easier to save this and only this entity without affecting other entities that might have been changed. I know that there is a parameter on the EntityManager.SaveChanges(...) method, but having it directly on the EntityAspect makes it a little more convenient.

    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 →
  11. Provide a link to WinJS

    Remove the need for jQuery and Knockout by linking it to WinJS ajax system and WinJS binding system.

    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. Improve mobile experience on the website

    The code samples appear to be fixed width and are difficult to view from iOS devices like the iPhone 5

    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 →
  13. breeze.js createError function can't handle datajs errors

    My ODataController Post method was updating its entity's CreatedOn property with DateTime.Now value before it's saving to database.

    Apparently datajs doesn't like DateTime.Now value and gives an error with "Invalid date/time value".

    File: datajs-1.1.2.js - Line 2133

    After datajs throws the exception, it falls to breeze.js createError function. However, since it's expecting error.response property, it fails to continue by giving "response is undefined" message.

    File: breeze.debug.js - Line: 15302

    I've updated the function by adding a check for response property;

    function createError(error, url) {
    // OData errors can have the message buried very deeply - and nonobviously
    // this code…

    11 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 →
  14. 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. BreezeJS and Moongose

    Hi All,

    I am new to MEAN stack, I am to easily for Moongose based apps and developed rapid prototypes in less than 30 mins, but with Zaa example even though I can run the sample in 10 mins. The concept of metadata generation with respect to MEAN stack very confusing, where as for .NET MVC example I can easily understand.

    12 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 →
  16. Flag which navigation properties have been loaded

    It's currently not possible to determine if a navigation property has been loaded.

    For example a order.orderLines. There is no way of knowing whether orderLines is empty because the order has no lines or that the navigation property has been loaded.

    This is a real pain when you have business logic that require the object graph to be loaded. This leads you to implement boiler plate data access related code to manually track which navigation property has been loaded - something that the breeze framework should be doing.

    This feature has been asked for on SO here: http://stackoverflow.com/questions/17798514/any-way-to-tell-if-a-breeze-navigation-property-has-already-been-loaded

    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. Breeze + Knockout validation -> new features

    If App uses breeze and ko validation, I suggest to

    add knockout validation rules for every fetched entity as showed in code example (here coffee code implementation for dataPropeties):

    addRules = (breezeEntity) ->
    return if breezeEntity.koValidationRulesAdded
    entityType = breezeEntity.entityType
    for property in entityType.dataProperties
    continue unless property.validators.length > 0
    do (property) ->
    displayName = property.displayName or property.custom?.displayName or property.name
    breezeEntity[property.name].extend
    validation:
    validator: (value) ->
    if breezeEntity.entityAspect.validateProperty property.name, {displayName: displayName, entity: breezeEntity}
    @message = ""
    return true
    else
    @message = breezeEntity.entityAspect.getValidationErrors(property.name)[0].errorMessage
    return false
    message: ""
    return
    breezeEntity.koValidationRulesAdded = true
    return

    this code allows:
    1) to validate single property with usage of all…

    5 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 →
  18. Tools for meta data creation for breeze not depending on a server-side ORM and tools for ORM-less server-code generation

    For me ia server-side ORM for a web application is a wrong cut. I think business logic should go as close to the data as possible to guarantee consistency, protection, and security. This means to me using stored procedures and database functions wherever possible (in a relational environment) and reasonable. In addition, if done right it's arguably unbeatably fast. The role of the Web API should be to provide access to the data across the network but not processing it.

    Let's suppose we have to query the database for all open orders for a certain customer including order items and…

    4 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 →
  19. Support for NotMapped properties server side

    it would be useful to have support for server-side properties notmapped together with the properties of normal db. Obviously readonly
    Thanks

    22 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 →
  20. Specify the version of Express to install in the Zza Example

    Express v4 differs a bit and will not work with the Zza Example. One recommendation would be to change the instructions until the express code is updated to: npm install express@3.5.1

    Once the code is updated to support Express v4, remove that specific version from the instructions.

    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 →
  • Don't see your idea?

1. BreezeJS Feature Suggestions

Feedback and Knowledge Base