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 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 →
  2. 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 →
  3. Paged query combining remote and cached data

    A Breeze plugin that pages a query combining remote and cached data in the query results. The paging strategy factors in pending, unsaved changes that could affect sort order (e.g., a name change), exclusion of entities marked for delete, and new entities that qualify for inclusion in the result. Could base it on the DevForce.EntityQueryPager (http://drc.ideablade.com/xwiki/bin/view/Documentation/query-paging)

    50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Propagate the .NET [RegularExpression] validation to the client

    [RegularExpression] should join [Required], [MaxLength], [StringLength] as a DataAnnotations validation attribute automatically propagated to the Breeze client through metadata. It's powerful. It should be relatively easy as it is string-based and regular expression specifications are (almost) the same in .NET and JS. See also [this StackOverflow question](http://stackoverflow.com/questions/16383161/regular-expression-server-side-unrecognized-by-breeze)

    50 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 →
  5. Http POST for Queries to enable advanced search screens

    When creating advanced search screen it's easy to hit the url limit of 2000 approx characters, certainly when performing projection queries.

    Allowing queries to be sent using Http POST would remove that restriction.

    Similar requests have been made on stackoverflow: http://stackoverflow.com/questions/18789860/breeze-js-in-clause-or-http-post-for-queries

    50 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 →
  6. Localization of validation error messages

    We are using BreezeJS in a fincancial bookkeeping DurandalJS/KnockoutJS based SPA.

    We have made a really nice reusable ui component for editing properties of breeze entities in the web ui, encapsulating label element + form field (with localized date/number formatting) + validation callout behavior showing the validation error messages.

    This editor component works really well; fueled by the breeze metadata providing extensive type information about properties we can dynamically display an appropriate form field, and the breeze validation framework helps setting maxLength to the form fields + required validation for non-nullable fields.
    We are also of course utilizing the extensible…

    48 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 →
  7. Allow for the filtering of Expands

    It would be most helpful if the results of an Expand could be filtered on the server-side. I.e, if you could have a particular Expand only ever include specific records. This would come in particular use when an institution utilizes "soft deletes", or needs to further filter those expanded records to only include those that should be visible by the current user.

    47 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Plugin for Ember.js

    Ember.js is a fastly growing and very impressive SPA web framework. Since Breeze is very well suited to OData this would give Ember developers who are developing against Microsoft and SAP a solid choice for their persistence layer.

    47 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 →
  9. ReactJs & React Native support

    Support for ReactJs and ReactNative including a the tutorial stream would be great.

    45 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 →
  10. 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 →
  11. 44 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 →
  12. JSON serialization of CLR Enum types (string/number) should be configurable (on the server/client)

    Hello. I am currently working in a project using BreezeJS with Entity Framework and TypeScript.

    I found it unfortunate that Breeze decided to change the server-side serialization of CLR Enum types from their numeric representation (usually int) to the string representation (.ToString()).

    TypeScript supports enum types, and by defining enums both on client and server, we could have a had type-safe, strongly typed enums also in our client scripts.
    The plan was to generate a TypeScript file containing all enums used across our entites as post-build-event using reflection.

    But after the Breeze serialization changed, this will not work.

    I would…

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. mongoose models to breeze.js metadata converter

    It would be nice to have a facility to create breeze.js metadata from existing mongoose models.

    38 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. Create function to translate error messages

    it would be possible to include a function to breeze similar to the included in knockout-validation to translate error messages:

    //quick function to override rule messages
    ko.validation.localize = function (msgTranslations) {

    var msg, rule;

    //loop the properties in the object and assign the msg to the rule
    for (rule in msgTranslations) {
    if (ko.validation.rules.hasOwnProperty(rule)) {
    ko.validation.rules[rule].message = msgTranslations[rule];
    }
    }
    };

    Related to: http://stackoverflow.com/questions/14316454/translate-breeze-validation-messages

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. JSON API, Ember.JS & REST Support

    - See http://jsonapi.org/ and http://jsonapi.org/about/ for more info
    - this will allow communicate Breeze using REST with other systems that supports or will support JSON API standard
    - Example for these system: Ember.js, Ruby ActiveModel::Serializers etc (http://jsonapi.org/examples/)
    - also see http://emberjs.com/guides/models/the-rest-adapter/
    - and https://github.com/emberjs/data

    38 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 →
  16. Provide a paired client side/server side validation module that would make it easier to apply the same custom validations on both the server

    This module would also have access to the user credentials associated with the end user performing the operation to be validated. Ideally, this would be configured via attributes as well as thru a programmatic API.

    37 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 →
  17. QueryInterceptors and ChangeInterceptor are needed to implement Security

    One needs to write lots of code to implement query and change interception to EF context. With interceptors we can easily do this with Breeze like WCF Data Services.

    35 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  14 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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 →
  19. Support the Azure Mobile Services

    It would be nice if Breeze directly supported Azure Mobile Services as a data provider/server endpoint. http://www.windowsazure.com/en-us/solutions/mobile/

    35 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. Extensible saveOptions and queryOptions can be interpreted on the server

    A mechanism for communicating extra material too/from the server method.

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

1. BreezeJS Feature Suggestions

Categories

Feedback and Knowledge Base