@esfaenza/forms-and-validations 11.2.144 → 11.2.145

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (6) hide show
  1. package/bundles/esfaenza-forms-and-validations.umd.js +1 -1
  2. package/bundles/esfaenza-forms-and-validations.umd.js.map +1 -1
  3. package/esm2015/lib/forms/base-form-control.js +2 -2
  4. package/fesm2015/esfaenza-forms-and-validations.js +1 -1
  5. package/fesm2015/esfaenza-forms-and-validations.js.map +1 -1
  6. package/package.json +1 -1
package/bundles/esfaenza-forms-and-validations.umd.js CHANGED
@@ -2043,7 +2043,7 @@
2043
2043
  }
2044
2044
  //Se mi arriva l'injectable del contesto posso capire se questo campo deve essere in readonly o no, solo se ho già inizializzato i controller custom dell'access control
2045
2045
  if (this.AppContext && this.AppContext.name && this.ACO_CUSTOMKEY && this.ac && this.ac.InitializedCustom) {
2046
- this.AppContextOwnership = !this.ac.has(this.ACO_CUSTOMKEY + ":" + this.AppContext.name);
2046
+ this.AppContextOwnership = !this.ac.has(this.ACO_CUSTOMKEY + ":" + this.AppContext.name, true);
2047
2047
  this._readonly = !this.AppContextOwnership;
2048
2048
  }
2049
2049
  ngControl.valueAccessor = this;