SEA to be my new ORM of choice

[adyba]

I like the code!!! I have seen several ng-ORM's already and this one has the cleanest code-base ever. I have some minor objectives that would prevent me from using this on my projects. Basically those are not big changes in terms of logic or core of the code, but can make huge difference in terms of usability.

• My BIG concern are ID's. I haven't tested it thoroughly but I'm bit afraid it would not support the database autogenerated ID's (ex ModgoDB uses _id, or Firebase $id, CouchDB _id again). The original POST call has no 'id' which is cool, but I'm not sure whether SEA recognizes downloaded MongoDB '_id' as a master_key property.
• I know this is just 5th commit but the new model properties url and settings are bit messy or at least undocumented. The extra settings object that should somehow configure the ngResource is undocumented at all. url is more a like route and settings.urlPrefix is just evil clown

[callebedrums]

Hi adyba.

Nice that you have liked my code.

Be free to fork, make changes and submit a pull request. I will be glad with your contribution.

• I agree with the ID's issues. As I am using Django + django-rest-framework and it generates the id automatic, I did not concern about it. Be free to make changes or to suggest how it should be implemented.
• I know that the code is not 100% perfect, and the are no docs for some thinks. I'm trying to write the doc, but I am not getting so much time to do it. You can note that english is not my primary language, so some times i mess up every thing. In the repository, there is a doc folder, and it is deployed on Read the Docs. I am getting some help of my young brother to review my text. I would be glad if you review it too.

Thanks for the feedback. I will try to improve SEA with your tips. When I do it, I will let you know.

[adyba]

I don't really understand the mechanism of configuration SEA from outside via defSettings, but I can still monkey-patch it ;) I'll do my best to create something like defSettings.masterKey and to convince SEA to use its value instead of simple id

[callebedrums]

Hi again.

I have created a branch, called iss1.

It has some changes to suport the masterKey configuration.

You can configure it using provider:

dashboard.config(function ($seaModelProvider) {
    $seaModelProvider.settings({
        masterKey: 'my_master_key'
    });
});

Or can set it on a single model:

return $seaModel.newModel({
    name: 'Modelname',
    masterKey: 'my_master_key',
    fields: {...}
});

Each instance will get a 'my_master_key' attribute. 'id' is the default.

I Will keep it on branch until i do enough tests. It is not stable, so if you find some bugs, let me know.

I hope I have helped.

[adyba]

You are damn fast ;)) Looking forward to test it against https://github.com/baugarten/node-restful