Use simple comparision in select rendering, so we can compare objects too. I do understand small performance decrease with this change, however I think objects as selection values worth it!
ngSelectOptions should accept expression instead of simple string object. Now we can pass whatever we want and it will be stored as option value. ATTENTION!: This commit breaks backward compatibility! You should update your options and use expressions instead of interpolations. See example changes in this commit for details
Since we have expressions in ngSelectOptions we don't have to convert strings to anything. Instead we should store whatever was passed to expression without any modifications.
Old commented code cleanup.
Use ngModel as model data binding for ngSelect. This will allow users to synergy with ngModel features like validations, forms etc.
Example for ngSelect usage with custom ngModel validations
We don't have to watch for model changes anymore. ngModel will do it for us
README Updated. Code cleanup
Merge pull request #4 from pluff/feature/obj_select_options

ngSelectOptions should accept expressions to allow passing any object as select value
Merge pull request #6 from pluff/feature/ng_model

ngSelect directive rewritten to use ngModel.