Patrick

My feedback

  1. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Patrick commented  · 

    Sorry it didn't seem to update me when you were commenting - apologize for not answering back.

    Let me test out passing the class to the metadata registration method and report back.

    We've toyed around with compiling (?) an ES6 class so you can use something like this and have it transformed in to metadata -

    ```
    class Person {
    @int32 id;
    @string firstName;
    @string lastName;
    }
    ```

    which would be equivalent (and possibly easier to write by hand) than the current metadata -

    ```
    metadataStore.addEntityType({
    shortName: "Person",
    dataProperties: {
    id: { dataType: "Int32", isPartOfKey: true },
    firstName: { dataType: "String" },
    lastName: { dataType: "String" }
    }
    });
    ```

    Adding the methods to the class could map to the current Breeze.js constructor method. Just some thoughts :)

    Patrick commented  · 

    Boo apparently I like Breeze too much and have posted too many votes in the past so I can't vote on this >.<

    Patrick shared this idea  · 
  2. 30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Patrick commented  · 

    Aurelia support is available via the Aurelia-Breeze plugin https://github.com/jdanyow/aurelia-breeze

  3. 79 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
  4. 202 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Patrick commented  · 

    ko.toJS() is a bad choice to use because the entire object graph is crawled and stringified by knockout. The more entities in local cache = the longer stringify takes.

    How to fix it?

    http://stackoverflow.com/questions/22550560/calling-ko-tojs-on-breeze-entity-causes-slow-long-running-script/22550561#22550561

    Patrick supported this idea  · 
  5. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Patrick commented  · 

    Woops I am sorry this was correct I made a mistake! Don't know how to delete it...

    Patrick shared this idea  · 
  6. 50 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Patrick supported this idea  · 
  7. 8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Patrick shared this idea  · 
  8. 214 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  1. BreezeJS Feature Suggestions  ·  Flag idea as inappropriate…  ·  Admin →
    Patrick commented  · 

    Here is a particular use case where this would be beneficial (for me at least : ))

    Assume that I have a web app that is using the Unit of Work and repository pattern. I want to define a specific save path when creating a new user (or requesting a user) so that certain tables that are not exposed to the client (specifically security information that resides on the server side only) have records created to allow the client to have a temporary user login security file created.

    (There may already be something to provide this by intercepting the saveChanges, but if there is I have not seen it / been able to do it with a unit of work YET)

    If I request a new user and call save changes, I am not able to intercept the new user to create it's temporary user security file. So far the only method I have found for this is to call save changes and then make an AJAX request to the server to create the security file, but that AJAX isn't a very secure / reliable way to request creation of a security file.

Feedback and Knowledge Base