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. Breeze Web API components should support async

    Both the Web API and EF 6 support async. All Breeze .NET server components should support async signatures and perhaps should deprecate the synchronous signatures.

    268 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Provide an Angular SPA template with full security

    VS2013 ships with a classic ASP.NET MVC template with full-feature identity management: login, password change, email validation, OAuth, etc, including both front-end and back-end code. However, there's nothing like this for a SPA using Web API 2.

    The suggestion is to provide a template/sample/demo based on Breeze and Angular for a Single Page App that implements all the identity functionality, plus provides some simple, replaceable demo of the business code that we developers want to focus on.

    102 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. MySQL + Node example

    B.MEAN example with MySQL

    7 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. 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. 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 →
  10. 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.

  11. 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 →
  12. Possible Bug

    Returns all records if Field name is same as search text.
    Go to Learn Breeze Step 6 of 6
    Change code to this:
    var p1 = Predicate.create("CompanyName", "contains", "CompanyName");
    var whereClause = p1;

    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. 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 →
  14. 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 →
  15. Support for MongoDB in ASP.NET Web API

    I'd like to use MongoDB with ASP.NET Web API. This would require translation of OData queries to MongoDB query syntax in C#, using the MongoDB C# driver.

    52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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. 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 →
  18. 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 →
  19. 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 →
  20. Validation integration with the FluentValidation framework.

    DataAnnotation is outdated and fills the POCO with dirt. FluentValidation support would be a great addition.

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

1. BreezeJS Feature Suggestions

Categories

Feedback and Knowledge Base