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
-
Support Swagger specification for metadata
Hi, the Swagger specs (https://developers.helloreverb.com/swagger/) looks like a good metadata provider for REST services.
If Breeze can leverage this, then it can potentially support much more web API implementations other than ASP.NET WebApi.
For example, ServiceStack supports the Swagger API via a feature (https://github.com/ServiceStack/ServiceStack/wiki/Swagger-API).
Cheers.
98 votes -
95 votes
-
Support other web apis, such as tastypie for Python/Django
Django and Tastypie expose data in a similar way to ASP Web API. It would be nice to have Breezejs work with Python frameworks.
91 votes -
Add the same tutorials for aurelia that you provide for angular and knockout
Provide the same tutorials for aurelia that you provide for angular and knockout is on my wishlist.
79 votes -
example using Dapper with Web API
I would be interested in seeing an example with Dapper and ASP.NET Web API, as mentioned in this stackoverflow post. http://stackoverflow.com/questions/16670151/using-breeze-js-with-dapper
77 votes -
Breeze clientside serialization of DateTimeOffset DataProperties
Thanks for addressing my case about supporting the CLR DateTimeOffset type in breeze (supported from v1.1.1).
Please look at this case for background information.
I have looked into how serialization of JsDate/DateTime/DateTimeOffset works in Breeze, and found a single shortage that defeats my idea of using DateTimeOffset on the server.
I believe that you will find my change suggestion reasonable.
In breeze, Dates are serialized in ISO-8601 format ("yyyy-MM-dd\THH:mm:ss.fffK") both by the breeze client and by JSON.NET configured by Breeze.WebAPI.
This is according to my expectations.When a DateTimeOffset is serialized by JSON.NET on the server, the timezone part of…
77 votes -
Metedata generator for poco classes using reflection
There needs to be a metadata generator for POCO classes in projects where entity framework in not used. Reflection can be used to findout properties for generating metadata.
77 votes -
Example of using metadata for validation with knockout.
Would be great to have an example of breeze exporting metadata for use with knockout validation.
76 votes -
for Linux
I quickly scanned the documentation about installation and found heavy reference to Visual Studio. While I have VS2008 installed on one of my PCs. My day-to-day working machine is a Ubuntu box. Could you show some instruction about using Breeze on a Linux box? Perhaps with Eclipse as the IDE. Or make Breeze available on an online IDE such as JS Fiddle? Thanks.
76 votesSimon,
Yes, our initial launch shows Breeze using Visual Studio 2012 with a .NET Entity Framework back-end.
Breeze does not require .NET, but this is currently how we have the data provider hooked up through WebAPI. We are planning to support other back-ends and front-ends, as well as show IDEs other than Visual Studio. Your feedback on UserVoice helps us prioritize these features.
Thanks for the feedback and your interest in Breeze.
-
Support DevForce models????
We have a lot invested in devforce models and the thought of having to maintain multiple models is troubling. I assume it is the saves that are the issue because I'm able to query the df entities without issue.
74 votes -
Integrate with SignalR
SignalR features auto-generated client proxies, and you don't need to follow silly conventions and/or decorate your method signatures with attributes to get them to work. You can design your Hubs the way you would design any other component in your solution, without having to be coupled to a protocol. Plus, you get duplex communications right out of the box. Please provide BreezeJS support for this valuable and intuitive technology.
72 votes -
Create linq like syntax for use with typescript
In jaydata it is possible to generate d.ts files for the entities. It is then possible to write queries like :
northwind
.Products
.filter( product => product.UnitPrice < 50 )
.orderBy ( product => product.Category.CategoryName )Note that full autocompletion is available for properties.
It would be great to have such a feature in breeze as well.
72 votes -
Integrate with KendoUI
I see Kendo doing work towards Breeze integration:
KendoUI datasource http://www.kendoui.com/blogs/teamblog/posts/13-02-21/breeze_js_and_the_kendo_ui_datasource.aspx
Kendo-labs repository
https://github.com/kendo-labs/breeze-kendoCan I hope that Breeze will pick up the torch and make some integration progress as well?
69 votes -
Support using stored procedures for retrieving data in EF
Using a sp in EF5 and have mapped the output to a complex type. Breeze doesn't seem to like that there is no key column, and not sure how to mark one as key so querying causes an error.
67 votes -
Indexeddb
Support for Indexeddb.
63 votes -
Support NancyFx
Add api support for NancyFx framework.
56 votes -
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 -
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 -
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 -
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
- Don't see your idea?