Nicolas comments

Repositories
Issues
Comments

Results 6 comments of


                                            Nicolas

Using before_save instead of after_update callback ?

i guess so, but asking users to call the AR **versioned** class method after the model's callbacks have been defined may solve this problem... Furthermore it would alow users to...

Separate Invitations table instead of adding more columns to Users

the last value of the code window should be console logged (maybe?)

findOrCreate can silently lead to model instances with changed attributes right after they have been initialized

For the ones who may have the same issue, I quickly added few lines to _prepareModel in order to clean changes after a potential attributes update ( line 1564) ```...

findOrCreate can silently lead to model instances with changed attributes right after they have been initialized

bbr 0.6.0 and backbone 0.9.2

Nicolas

Using before_save instead of after_update callback ?

Separate Invitations table instead of adding more columns to Users

the last value of the code window should be console logged (maybe?)

findOrCreate can silently lead to model instances with changed attributes right after they have been initialized

findOrCreate can silently lead to model instances with changed attributes right after they have been initialized

Upgrade AA dependency to 1.0.0.pre2