Hi,
Considering it is resolved, I am closing this issue.
Have a nice week.
Hi,
Is this issue resolved?
Have a nice week.
Hi,
I am closing the issue. Please feel free to reopen it if it is not resolved.
Have a beautiful week.
Hi,
Closing this issue. Please feel free to reopen it if it is not resolved.
Have a nice week.
Hi,
The document is live.
https://docs.abp.io/en/commercial/latest/ui/angular/lookup-components#lookup-typeahead-component
Please let me know if this document satisfies your question.
Have a nice day.
Hi,
I am currently working on the documentation and very close to finish it. I will share it with you soon.
Hi,
Is this issue resolved? Can we close it?
Hi hilal.aksoy,
You can set the disabled property of the component to true. Here is an example:
<abp-lookup-select
[disabled]="true"
cid="authorIdFilter"
[getFn]="service.getAuthorLookup"
[(ngModel)]="filters.authorId"
[ngModelOptions]="{ standalone: true }"
></abp-lookup-select>
Please note that, if created by ABP Suite, there are two instances of abp-lookup-select on the same page: one inside the create/update form and another one in the advanced filters.
Hi,
I have tried your scenario and could not reproduce the problem. Suite generated the Angular UI successfully.
Hi sgal,
We can reproduce the error you got with Node v15 and npm v7, but these are not the versions we support. Angular CLI has known problems with these two versions and we do not know when they will be ready to use.
Could you please try with Node v14 and npm v6?
Thanks.