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
-
Possible copy/paste error in "Or" predicate documentation
Hi there, love your work, breeze rocks, I just noticed the Or predicate documentation looks suspiciously like the And documentation :-)
1 vote -
Add decimal precision and scale to metadata
t doesn't appear as though the breeze metadata includes the precision and scale of decimal types. It simply identifies a property as "Decimal". The information is available in EF models. Is this something that could be added to the metadata and retained in dataproperty?
I believe similar attributes may be useful for other numeric types.
15 votes -
Support expand('entity1, entity2, entity3') of multiple entities from a TPH type
Currently if I try to expand a type that is a TPH with more than one entity in the expand, Breeze throw an error.
see link for details of odata results
http://stackoverflow.com/questions/16727828/breeze-doesnt-expand-tph-entities-correctly3 votes -
Integrate Breeze with Salesforce
Smooth the integration process for companies who'd like to incorporate Breeze into their Salesforce deployments.
1 vote -
Integrate Breeze with SAP BW
Smooth the integration process for companies who'd like to incorporate Breeze into their SAP BW deployment.
1 vote -
Integrate Breeze with SAP ERP
Smooth the integration process for companies who'd like to incorporate Breeze into their SAP ERP deployment.
1 vote -
Add missing MetadataStore functions for Typescript
The
setEntityTypeForResourceName
method of theMetadataStore
class does not exist in TypeScript definitely typed d.ts file. This appears to be a method of the public API (since the unpublished TempHire sample app calls this method) but it is not accessible to TypeScript because there is no definition for it. Suggest to define this missing method. There are a few others too: getEntityTypeNameForResourceName, getIncompleteNavigationProperties, etc...5 votes -
Better support for ordering by navigation property
When ordering by a navigation property and using skip-take pagination, skip-take is processed before the ordering, which is counter intuitive. You get this:
Page 1: A, B, C, D
Page 2: A, B, C, DInstead of
Page 1: A, A, B, B
Page 2: C, C, D, DWhen using query.from('Foo').expand('Bar').orderBy('Bar.A').skip(10).take(10). It works as expected when ordering by a regular property of Foo.
2 votes -
Support the $callback query string parameter for the BreezeController
I would like to use the BreezeController with Kendo UI Grid, using Kendo's native ODATA support, but it requires that the $callback paramter be supported.
13 votesAdam,
I’m not sure about this one. We’d like Kendo devs to use Breeze for data mgmt rather then Kendo. Can you provide use with a detailed use case for this?
Regarding $callback, definitely. Support for JSONP would be very valuable. Let’s get some votes on this one. :)
-
Log object value in error message
Any time an error message logs or pops referencing a data or object
error, it would be nice that you include in the log the data or object value so we can explore and see what you are getting from us. I belive this is an easy and speedy fix and it will help us a lot. :)3 votes -
Not assume identity columns are part of a primary key.
Throughout breeze it is assumed that if an entity has an identity column, that column is part of the primary key. Identity columns do not have to be part of the primary key.
3 votes -
Expose the DisplayAttribute Name property in the Metadata
I would like to expose the Name property of any model properties decorated with the DisplayAttribute, so I can use it to display more user friendly messages. This should work automatically with an EF context provider, but should also be available to a custom provider.
The default validation should also look for this value, and use it instead of the field name.
5 votes -
Demonstrate How to Debug Metadata Exceptions
If I navigate to api/breeze/metadata, it returns proper json for my Entity Framework DbContext. However, when called from the app, it just returns Metadata queryfailed, NaN. Would be good to know what is wrong. I have unit tested the context and it is fine. Perhaps a validation screen where you paste in your json and it tells you what is wrong or not supported. thanks.
4 votes -
EntityManager validation
Allow validators to be added to the EntityManager right away, have EM 'hold' them until MetaData is retrieved, and than add them accordingly. Instead of putting that on the client of EM...
4 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 -
Repository sample that serves view models.
Use the new json schema to get a controller to return a proper view model instead of what is essentially a domain object.
The idea here is to essentially create a custom provider that connects to a web api that returns view models and when the are returned back. an overridden save changes parses things out and submits them back to EF as domain objects and does whatever needs to be done
Love the project keep it up
7 votes -
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 -
Can configure a parent entity type to enter the modified state when a child changes
Often (but not always), the parent is the root entity of an aggregate. An Order is the root of an Order aggregate with child line items. When a line item is added/deleted/modified the semantics say that the Order has changed. The concurrency check on the Order governs the entire graph. So we want any line item change to force the Order to be changed. The developer should be able to specify in metadata that the Order changes when anything in its line items collection changes. The specification should be on a navigation path basis. Breeze should respond accordingly
22 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
-
Add the possibility to pass one call specific argument to the ajax adapter
I want to do some stuff inside the ajax adapter, that depends on who initiated the call. For example tracing. In order to do that I need to be able to pass an argument to Breeze that is forwarded to the ajax adapter.
3 votes
- Don't see your idea?