Added tag condition #angular.dataView.hasEnumTypeField for applicability of the AngularEnumTypes Feature
Added nativeTypes for TYPESCRIPT technology in the EnumTypeBuilder for the following concerns: json, transport, json-transport, transport-json.
json still uses the string type as this backend exposes it this way.
transport now uses Reference from the NSX Angular Runtime Library.
json-transport maps the string value into a Reference with both id and displayLabel equal to the string value.
transport-json maps the Reference.id into a string value.
Added Expander Features with Reference imports for all angular-expanders that use the transport - TYPESCRIPT nativeType to ensure the import is present.
Added some missing tests to check component, service, regular imports on all Expander Features. Some TestClasses did not check imports, etc.
Changed nsc-select-components in filter-, add- and edit-forms to use formControlName with the formControlName of the actual FormModel field instead of using the separate formControl.
Support edit-form initialization with null values explicitly.
Changed Detail and Table Expander Features to use id of enumReference for building the translationKey.
Changed DetailHtmlExpander Feature to use the inputSignal method-call instead of trying to access the model as a variable.
Removed the standalone enumFieldFormControls and syncing code in angular filter-, add- and edit-forms.
Removed the takeUntilDestroyed, FormControl and DestroyRef imports in enum-type-angular-expanders Expander Features. These will now need custom imports if you used them in custom code.
Fixed an issue where the value of an enum field is not filled in the edit page (angular-expanders)
Fixed an issue where a duplicate anchor name can occur in the new and edit HTML (angular-expanders). Beware: this changes the name of the 'custom-form-field-type-attributes' anchors, you will need to fix these harvest files manually.