Rohit Sharma

It was done intentionally in #32024 :slightly_smiling_face: There was a reason for the change, see [the issue](https://github.com/twbs/bootstrap/issues/31202) for more information. /CC @twbs/js-review

As you can see [here](https://angular.io/api/forms/NgModel#selectors), we can not use `ngModel` with the `formControlName` or `formControl`. As the selector for the `ngModel` is: ```javascript [ngModel]:not([formControlName]):not([formControl]) ``` So, now the example shown...

@Tephrosis, I used it in my last project only. Further, I am thinking about https://github.com/sideway/joi, which seems powerful.

Basically, the idea to expose few options from the config of the Popper was that those options were either customized by the bootstrap (mostly) or there was any other specific...

Shortly, there may be any solution to accept the options for the popper configuration dynamically. That makes it possible to omit the requirement of the stringified JSON in the data...

So do you guys want the hide method to work synchronously? :worried: Since the code that you wrote is fine IMO @alpadev ```js const modal = bootstrap.Modal.getInstance(modalEl); modal.hide(); modalEl.addEventListener('hidden.bs.modal', ()...