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
-
Warn about "entityType" reserved property name in NamingConvention
The NamingConvention documentation at http://breeze.github.io/doc-js/server-namingconvention.html must warn developers that the property name "entityType" cannot be used by any entity data on the client-side, because it conflicts with the metadata stored in "entityType" of each client-side record managed by breeze-client Entity. Specifically, the function serverPropertyNameToClient cannot return "entityType".
The only indication is the unhelpful "Cannot assign a navigation property in an entity ctor.: entityType" error thrown by adapter-model-library-backing-store.ts. The "entityType" property does not have to be referenced in application code. Any property name received from the server that resolves to "entityType" will trigger this issue.
In fact, you don't need a…
3 votes -
Flagged Enum Filter Support
Add support for properly filtering flagged enums.
3 votes -
Can Breeze support Common Table Expression Recursive Query
Hi,
I am using BreezeJS alongwith angular. I would like to know if BreezeJS can support Common Table Expression alongwith othere Breeze predicates.
Thanks,
Dhanaji1 vote -
Add PATCH verb to breeze
I keep having to add the PATCH verb into the breezejs framework so that it is compatible with ODATA3. This needs to be done in the createChangeRequests function
1 vote -
Firebase Support?
I read in the documentation that Firebase was supported. Is there a way to use Breeze JS with Firebase 3?
4 votes -
The online tutorial is broken again.
Just tried and it is not working.
Thanks
1 vote -
XML metadata from WCF Data Services
Breeze doesn't seem able to consume the XML metadata from WCF Data Services, it wants it in JSON format. Can't find any good workarounds.
4 votes -
Make unit tests for breeze.js independent of server technology
Currently it appears as though all of the unit tests for breeze.js require Visual Studio and an external data source. Similarly to a previous request, mock ajax requests for unit tests in the breeze.js repo. This would make it easier for people to test potential pull requests for breeze.js.
2 votes -
Support evaluation of custom Annotations for Enums through the meta data
If I crete an "advanced" ENUM on server side, including custom annotations, I would like to be able to use that ENUM at client side without redefining it there. Following method can be used to automatically create enums on client side as global variables. In addtion to that I would like to be able to evaluate annotation metadata of the ENUMS to transfer the data that is given by my custom Annotations.
fetchMetadata()
.then(function(data) {
…//create global ENUMs from breeze meta data //see http://stackoverflow.com/questions/15732072/dropdown-filled-with-options-provided-by-an-enum-server-side-with-breeze var enumTypes = data.schema.enumType; var size = enumTypes.length; if (size == null) { createGlobalEnum(enumTypes); } else
2 votes -
Exclude entire entities from metadata (EF backend)
I've seen some SO topics on excluding individual entity properties, but have not figured out a way to exclude entire entities.
3 votes -
rethinkdb and aurelia
add support for rethinkdb and aurelia
30 votes -
Change entityAspect name to $entityAspect to prevent angularJS.equal in circular reference
Angular is comparing objects by the equal function.
If you have a watch on a breeze entity the entityAspect object will cause the ng.equal function to produce a stack overflow.
objects with the $ prefix are ignored by ng.equal function.In my case I had an issue with ng-formly and breeze because formly is watching the collection and so also the entityAspect.
25 votes -
Support ES6 class definitions for client-side modeling
With ES6 classes we now have a way to define classes better than ever before in ES6.
- Support defining metadata client-side via ES6 classes
- Support adding methods and such via the classes instead of via the initializers (ex - computed properties as getters, methods on the class instead of adding to the initializer / constructor)
- Default values if not supplied
6 votes -
Looking for breeze to rock SharePoint data
I am just looking if Breeze has already working with SharePoint data,
1 vote -
Don't initialize property values
Currently, when breeze creates a new entity it initializes each property based on its type. Uses 0 for an int, empty for string and so on. It uses null for a nullable property. Seems reasonable until you actually use it. When I create a new entity, I want it to fail validation until the user actually fills in values. For non-nullable types, I want null. Otherwise, the user might accidentally save the default value -- which almost certainly is wrong for them. For a nullable type, it would be nice to initialize to value that's invalid ... other than null.…
2 votes -
Fire event on metadata FETCHING (not just fetched
There is a helpful event for metadataFetched. However, it would be even more helpful to also add an event right BEFORE the metadata request is sent out.
My use case for this is I am showing textual progress updates on screen, and I would like to update the message when metadata is fetching. I can use the "Fetched" event to show that we are done, but would need a "Fetching" event to indicate when we start.
1 vote -
breeze-node
the tutorial should contain Node.js part
2 votes -
Northwind example with Java Spring & Hibernate
Hi,
I have downloaded java northwind example from github (https://github.com/Breeze/breeze.js.samples/tree/master/java/NorthBreeze)
Then i create northwind database and deploy server with Java. The server return data and metadata json look good.
But when i deploy client and call server, i received error:"Metadata query failed for: http://localhost:8081/NorthBreeze/breeze/northbreeze/Metadata. Unable to either parse or import metadata: Error configuring an instance of 'NavigationProperty'. The 'foreignKeyNamesOnServer' parameter is optional or it must be an array where each element must be a 'string'; [object Object]"
Here is my Medata JSON return, please see this file in URL:
Can anyone help me?
Thanks very…
18 votes -
Include Navigation Properties in BeforeSaveAllEntities save maps
Currently passing entity with navigation properties to the client. Once client modifies the entity or the navigation property entities they come back to the server during save separated making us write more code to perform validation and server side business logic.
EXAMPLE: I have a class called WorkOrder, Payment and Customer. The structure of the class is as follows:
WorkOrder
- WorkOrderID int
- WorkOrderNumber guid
- CustomerID int
- PaymentID int
- ExclationLvl intPayment
- PaymentID int
- PaymentType int : reference lookup table called PaymentTypes which has the payment types (ie: Credit Card, Check, Paypal)
- Amount…6 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
- Don't see your idea?