A form value can be an old one

[maxime1992]

This is a tricky issue to repro and will probably only repro through a test to get the timing right.

But I just hit a case that drove me insane where my form was considered valid, while the value that was passed clearly wasn't.

@zakhenry and I identified the potential issue and it might be coming from the fact that we do:

 this.subscription = this.formGroup.valueChanges
      .pipe(
        // ...
        delay(0),
        map(changes => {
          this.onChange(changes)
        }),
        // ...
      )

But apparently that value coming from the form might not be mutated like I thought it'd and thus, the validity check would succeed on the RootFormComponent because the form might now be valid while sending the previous value.

[maxime1992]

🎉 This issue has been resolved in version 2.11.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀