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.

  1. Support for query parameters

    Something like

    var query = new EntityQuery()
    .from("CustomersStartingWith");
    query.parameters.add("A");

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Build 0.76.2 adds a new EntityQuery method: withParameters.

    This method allows custom parameters to be passed to any server side method, in addition to those that Breeze uses for its normal querying. Custom parameters can be mixed in with other query clauses.

    For example:

    var query = EntityQuery.from(“EmployeesFilteredByCountryAndBirthdate”) .withParameters({ BirthDate: “1/1/1960”, Country: “USA” }) .where(“LastName”, “startsWith”, “S”) .orderBy(“BirthDate”);
  2. Attribute on controller actions to limit result size

    Add an attribute that can be placed on a Web API controller action to limit the number of entities that can be returned in this query.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Attributes on controller actions to block the use of Select and Expand

    Define attributes that block the use of Select and Expand.

    13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    Attributes for blocking Select and Expand were added a few builds ago, but we’re marking it complete on UserVoice today. Sorry for the delay.

    Breeze 1.3.1 is now available, including Inheritance and OData writes/saves.

  4. Naming convention for mapping metadata names

    A mapper should accept filters that can do the mapping automatically. CamelCasing is one such filter. Another might do something nice with stuff like "First_Name", "Last_Name", etc.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Metadata name mapper for the client

    Add a mapping mechanism in the metadata on the client that lets us have the names we want.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 48 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 233 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  Flag idea as inappropriate…  ·  Admin →
1 2 4 Next →
  • Don't see your idea?

1. BreezeJS Feature Suggestions

Categories

Feedback and Knowledge Base