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.
272 results found
-
932 votes
To accelerate the development of this particular feature we are seeking user support through crowdfunding.
Want to learn more? Send us an email at breezeadmin@ideablade.com and we’ll send you details on how you can participate.
Thanks for helping us make BreezeJS the best open source project on the planet!
-
Provide a ServiceStack adapter
Support ServiceStack much like ASP.NET Web API is supported
518 votes -
Use websockets/signalr to push updated objects instantly out to the client cache
On the client side, objects can get stale if they are frequently updated. Instead of requiring constant polling to see if entities have changed, allow updates to be pushed from the server out to the client cache. That change would in turn trigger knockout bindings so that the HTML instantly updates.
385 votes -
Better documentation to create own support for any external datasource
What needs to be considered on client/server side etc.
Maybe with a sample?345 votes -
341 votes
-
Support .NET Validation Attributes
It would be great if the .NET validation attributes defined on the business model were sent along with the metadata. One benefit of this feature would be that we wouldn't have to redefine error messages on the client side.
278 votes
AdminAdmin
(Product Manager, Breeze.js)
responded
A quick update for this request:
We’re probably 50% there today, but hope to get to 80% soon. This is certain to get done, but we’re just not there yet.
-
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#_Toc365046429243 votes -
228 votes
-
RESTfull conception support
RESTfull concept suggests to use different http methods(get/post/put.delete) for CRUD operations with specific request params and responses. Also it suggests send only necessary info.(for ex. no need send entityAspect for RESTfull API).
Similar functionality exists in JayData. Will be great if Breeze will support this functionality too. It'll be usefull for big apps, for api which have to be shared to other clients and expand area of usage.
Also this functionality will add supporting DTO without writing own context provider for breeze.webapi .net framework because in this no need to use breeze.webapi .net. Generally users will develop asp.net web api…
214 votesA quick update for this request:
We’re substantially there, but we still need to make the experience better. We’re still working on this.
-
Support for "in" query
For example in sql:
Select id, name from table1 where id in (1,2,3)
213 votes -
204 votes
We’re looking at providing better documentation regarding how a developer might provide their own support for any external datasource.
-
Expose a method on the EntityManager to "unwrap" an entity instance (toJS).
There are a few use cases where an entity instance needs to be sent to the server to an MVC API controller (for example for async server side validation); to do this, it is necessary to obtain an unwrapped version of the instance (plain JSON) that contains no internal properties such as entityAspect and uses properties instead of observables (ko.mapping.toJS is not suitable because of the former). Also, because the client configuration allows for a different naming convention, the method should be able to translate the names back to the naming convention originally used by the server.
Such a method…
202 votes -
Support Design Time Typed Entities
A tool to create Typescript typed entities from WebAPI metadata in the same way that JaySvcUtil works for JayData
182 votes -
150 votes
-
Give the developers more extensibility on the metadata creation.
Sometimes it is needed to change the metadata at run time on either the client or the server. It would be nice to be able to have a mix of automatic metadata creation (through EF) and manual manipulation. An example of this need could be for server side encrypted properties and the need to add a new property with the unencrypted value. Read this question on StackOverflow for more info: http://stackoverflow.com/questions/18118091/how-to-add-a-property-to-an-entitytype-after-it-has-been-added-to-the-data-store
128 votes -
124 votes
-
Update samples to use typescript
Provide samplese that use breeze and typescript
114 votes -
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 -
To add the java backend for the breezejs.
right now breezejs is running on asp.net(as a backend) but since I am a developer of Java Applications that's why I am waiting for the java version of the breezejs
101 votesWork is well underway on a Java backend for Breeze, using Hibernate. Please check out https://github.com/Breeze/breeze.server.java/tree/master/breezejs-hibernate
-
Integrate Breeze with FluentValidation
I have used FluentValidation with mvc for some years now. And enjoy the excellent client side validation it's provide.
Is there a way to use FV with Breeeze? I am about to refactor a part of an existing application to SPA ala HotTowel
99 votes
- Don't see your idea?