Add formsModule to extensible-form-prop component, enhancement for template and fix className duplication #18962
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related question -> https://support.abp.io/QA/Questions/6582/TenantOrganizationUnit-extra-properties-which-are-navigation-properties-cause-frontend-error-afer-update-to-ABP-802
Resolves https://github.com/volosoft/volo/issues/16571
I guess this error is happening because of we moved extensible-form-prop component to standalone and missed the import formsModule.
Previously it was exported from ui-extension.module. This module is importing CoreModule, and CoreModule imports FormsModule.