docs(examples): migrate content-full-layout-scroll example to use rxResource

[mistrykaran91]

---

Documentation.
Examples.
Dashboards Demo.
Playwright report.

Coverage Reports:

• charts-ng
• dashboards-ng
• element-ng
• element-translate-ng
• maps-ng
• native-charts-ng

[gemini-code-assist]

Code Review

This pull request refactors the component to use Angular signals and rxResource for data fetching and state management, removing manual change detection and subscriptions. The review feedback suggests removing the hardcoded page limit in favor of dynamic values from the page signal, making setPage private, and simplifying the isLoading signal by avoiding an unnecessary computed wrapper.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Instead of using the hardcoded maxPageNumber (which is limited to 10), bind [totalPages] to the dynamic totalPages property from the page() signal. This ensures the pagination correctly reflects the actual number of pages available from the service.

Suggested change

	[totalPages]="maxPageNumber"
	[totalPages]="page().totalPages"

[gemini-code-assist]

Update setPage to dynamically limit the requested page using this.page().totalPages instead of the hardcoded maxPageNumber. Additionally, since setPage is only called internally by setPaginationPage, we can change its visibility to private.

  private setPage(pageRequest: PageRequest): void {
    const totalPages = this.page().totalPages;
    const requestedPage = totalPages > 0 ? Math.min(pageRequest.offset, totalPages - 1) : pageRequest.offset;
    const current = this.pageRequest();
    if (current.offset !== requestedPage || current.pageSize !== pageRequest.pageSize) {
      this.pageRequest.set({ ...pageRequest, offset: requestedPage });
    }
  }

[gemini-code-assist]

Since isLoading() is now a boolean signal, we can bind it directly to [ghostLoadingIndicator] without the > 0 comparison.

Suggested change

	[ghostLoadingIndicator]="isLoading() > 0"
	[ghostLoadingIndicator]="isLoading()"

[gemini-code-assist]

Remove the hardcoded maxPageNumber property since the total number of pages should be dynamically retrieved from the page() signal.

Suggested change

	protected readonly maxPageNumber = 10;
	private readonly pageRequest = signal<PageRequest>({ offset: 0, pageSize: 10 });
	private readonly pageRequest = signal<PageRequest>({ offset: 0, pageSize: 10 });

[gemini-code-assist]

With the migration to rxResource, this.dataResource.isLoading is already a boolean signal. Avoid creating an intermediate computed signal just to read another signal's value, as the value from a signal is already memoized. We can assign the signal directly.

Suggested change

	protected readonly isLoading = computed(() => (this.dataResource.isLoading() ? 1 : 0));
	protected readonly isLoading = this.dataResource.isLoading;

References

1. Avoid creating an intermediate computed signal just to read another signal's value. The value from a signal is already memoized, so an extra computed signal is redundant.