Different behaviour than previous version about angular-input-modified HOT 4 CLOSED

Hello @tarik81!

Thank you for your interest in this module and for your bug-report.

Starting from the version 2.0.0 the module is using a more robust way to initialize he master value of the ngModel. It is introduced in this commit. You can see that the initialization flag is now used instead of the typeof comparison.

You can see it in the changelog:

#8: "Doesn't work when bound object member isn't set" (thanks to Chris Yates). We are now using a more robust way to initialize master value (initialization flag).

I'm sorry for the inconvinience it may caused you. However, it can be a backward-incompatible change, but it is introduced in the major update, so this is prefectly fine with the SemVer specification. I will update the changelog to outline this issue for other migrating users.

Thank you!

from angular-input-modified.

Considering your use case I will recommend to fetch the data in the resolve stage of your routing. The best approach is to always initialize the form data synchronously with the controller execution (i.e. without a delay).

If my answer solved your issue - please consider to close it. If you have any other questions - I will be glad to assist you. Cheers!

from angular-input-modified.

I've updated the Changelog and also added a section to the README on the topic of form initialization, please see it here: https://github.com/betsol/angular-input-modified/blob/master/readme.md#form-initialization.

from angular-input-modified.

That solves my issue, thank you :)

from angular-input-modified.