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 -
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 -
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 -
228 votes
-
150 votes
-
341 votes
-
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!
-
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 -
32 votes
-
[FlagsAttribute] enums should be an array on client-side
Enums that are marked with FlagsAttribute are not properly kept on client side. They are always a string separated by comma ","
Bummer. It should be an array so it would fit nice with ko` checked binding.Besides it would be much easier to work with them.
They should be serialzed (coerced) with comma when sent to the server only!15 votes -
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 -
rethinkdb and aurelia
add support for rethinkdb and aurelia
30 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); } else2 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
- Don't see your idea?