adf-aspect-list: Cannot display more than 100 items

[ath-atolcd]

Current behavior

The Aspect List component is limited to displaying a maximum of 100 items. The maxItems parameter is by default 100, preventing users from viewing or managing more than 100 items in the list, regardless of how many items are actually available.

Expected behavior

The Aspect List component should be able to display all available items without artificial limitations. Either the maxItems limit should be configurable for the component to allow displaying more than 100 items when needed.

Steps to reproduce the issue

1. Open the edit aspects button with more than 100 items in the Aspect List
2. Notice that only the first 100 items are displayed
3. Items beyond the 100th item are not visible or accessible

Component name and version

• Component: adf-aspect-list
• ADF Versions affected: 8.1.1, 6.1.0, 6.9.0

Environment

• Browser: Firefox Version 145.0.1 (64 bits)
• Node version: 14.20.1

[ath-atolcd]

Temporary workaround

While waiting for an official fix, a temporary workaround for 6.9.0 can be applied by overriding the AspectListService in your module.

{ provide: AspectListService, useClass: CustomAspectListService }

@Injectable({
  providedIn: 'root',
})
/**
 * Override of AspectListService to allow a maxItems value greater than 100
 * for the getCustomAspects method.
 */
export class CustomAspectListService extends AspectListService {

  constructor(
    alfrescoApiService: AlfrescoApiService,
    appConfigService: AppConfigService,
    private readonly appConfig: AppConfigService
  ) {
    super(alfrescoApiService, appConfigService);
  }

  override getCustomAspects(whiteList?: string[]): Observable<AspectEntry[]> {
    const where = `(not namespaceUri matches('http://www.alfresco.*'))`;
   // or your custom path in config.json 
    const maxItems = this.appConfig.get<number>('aspectListService.maxItems', 200);

    const opts: ListAspectsOpts = {
      where,
      maxItems,
      include: ['properties'],
    };

    return from(this.aspectsApi.listAspects(opts)).pipe(
      map((result: AspectPaging) =>
        this.customFilterAspects(whiteList, result?.list?.entries ?? [])
      ),
      catchError(() => of([])),
    );
  }

  // The original method in the parent service is private, so we reimplement it here
  private customFilterAspects(
    visibleAspectList: string[] | undefined,
    aspectEntries: AspectEntry[]
  ): AspectEntry[] {
    if (!aspectEntries) {
      return [];
    }

    if (visibleAspectList && visibleAspectList.length) {
      return aspectEntries.filter((value) =>
        visibleAspectList.includes(value?.entry?.id)
      );
    }

    return aspectEntries;
  }
}

The same logic also applies to later versions.