From 533637492d988f3ebd6343816f3b16e9a24b9a88 Mon Sep 17 00:00:00 2001
From: nprol <134269709+nprol@users.noreply.github.com>
Date: Tue, 16 Sep 2025 10:43:25 +0200
Subject: [PATCH 1/2] Remove duplicate query-rows input (#692)

Co-authored-by: Noelia Prol Carballo <noelia.prol@imatia.com>
---
 docs/components/data/35-o-table.component.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/components/data/35-o-table.component.md b/docs/components/data/35-o-table.component.md
index 4d24f9501..95f350cd9 100644
--- a/docs/components/data/35-o-table.component.md
+++ b/docs/components/data/35-o-table.component.md
@@ -1366,7 +1366,7 @@ Global default autoadjust can be specified by providing a value for O_TABLE_GLOB
  <o-table fxFlex attr="customers" title="CUSTOMERS" service="customers" entity="customer" keys="CUSTOMERID"
     columns="CUSTOMERID;PHOTO;NAME;SURNAME;ADDRESS;STARTDATE;EMAIL;CUSTOMERTYPEID"
     visible-columns="PHOTO;NAME;SURNAME;STARTDATE;EMAIL;ADDRESS;CUSTOMERTYPEID" sort-columns="SURNAME" query-rows="10" quick-filter="yes"
-    row-height="medium" select-all-checkbox="true" pageable="yes" fixed-header="yes" query-rows="25" auto-adjust="yes">
+    row-height="medium" select-all-checkbox="true" pageable="yes" fixed-header="yes" auto-adjust="yes">
     <o-table-columns-filter columns="STARTDATE;SURNAME"></o-table-columns-filter>
     <o-table-column async-load="true" width="48px" attr="PHOTO" orderable="no" searchable="no" type="image"
       image-type="base64" empty-image="assets/images/no-image.png" avatar="yes">

From 03f3f814107717644d47d897d23d87e503199daf Mon Sep 17 00:00:00 2001
From: nprol <134269709+nprol@users.noreply.github.com>
Date: Fri, 26 Sep 2025 09:28:36 +0200
Subject: [PATCH 2/2] Indentation fixed at html examples from o-list-component
 docu (#694)

Co-authored-by: Noelia Prol Carballo <noelia.prol@imatia.com>
---
 docs/components/data/34-o-list.component.md | 24 ++++++++++-----------
 1 file changed, 11 insertions(+), 13 deletions(-)

diff --git a/docs/components/data/34-o-list.component.md b/docs/components/data/34-o-list.component.md
index ca1780133..bc68a43d9 100644
--- a/docs/components/data/34-o-list.component.md
+++ b/docs/components/data/34-o-list.component.md
@@ -67,7 +67,7 @@ You can see an example of this component in the [OntimizeWeb playground]({{site.
 The `o-list-item-card` component is used to display a card list item with text, image and action buttons.
 
 ```html
-	<o-list #list attr="list" title="List" columns="id;name;username;email;street;phone" keys="id"
+<o-list #list attr="list" title="List" columns="id;name;username;email;street;phone" keys="id"
   [static-data]="getStaticData()" refresh-button="true" quick-filter="true" insert-button="false"
   row-height="medium" detail-mode="none">
   <o-list-item *ngFor="let row of list.dataArray">
@@ -109,7 +109,7 @@ You can see an example of this component in the [OntimizeWeb playground]({{site.
 When building an `o-list` component you can include one of the predefined list items the **OntimizeWeb** offers or you can include your own list item. For including a custom list item, **OntimizeWeb** offers the `o-list-item` directive that can be attached to an angular material list item (`mat-list-item`) or an angular material card (`mat-card`).
 
 ```html
-	<o-list #list attr="list" columns="id;name;username;email;street;phone" quick-filter-columns="name;username" [static-data]="getStaticData()">
+<o-list #list attr="list" columns="id;name;username;email;street;phone" quick-filter-columns="name;username" [static-data]="getStaticData()">
   <mat-card *ngFor="let row of list.dataArray" [o-list-item]="row">
     <mat-card-header>
       <div mat-card-avatar>
@@ -131,18 +131,16 @@ The `o-list` component allows to add content in the toolbar with the selector `o
 If the selector `o-list-toolbar` is used together with `position='start'` the content will always be placed to the right of the New/Refresh/Delete buttons and if used together with `position='end'` the content will always be placed to the left of the quickfilter
 
 ```ts
-<o-list #list attr="list" ... refresh-button="yes" quick-filter="yes"...>
+<o-list #list attr="list" ... refresh-button="yes" quick-filter="yes"... >
   <!-- Custom content toolbar in position start -->
-  <o-combo o-list-toolbar position="start" label="Sort" width="100px"...></o-combo>
+  <o-combo o-list-toolbar position="start" label="Sort" width="100px"... ></o-combo>
   <!-- Custom content toolbar in position end -->
-  <o-slide-toggle o-list-toolbar position="end"....></o-slide-toggle>
+  <o-slide-toggle o-list-toolbar position="end"... ></o-slide-toggle>
 </o-list>
 ```
 
 ![Add custom content in toolbar in position start]({{ "/assets/images/components/list/add-content-toolbar.png" | absolute_url }}){: .comp-example-img}
 
-
-
 ## Pagination <span class='menuitem-badge'>new<span>
 
 By default, the list is not paginating the data, but if you want that behaviour you must set `pagination-controls= "yes"` in the o-list component.
@@ -156,9 +154,9 @@ You can also configure the number of records initially displayed with query-rows
 Ontimize web now supports the JDBC **UUID** sql type. To indicate that a key column is of type UUID, all you have to do is to set to set the **UUID** via input `keys-sql-types` in the `o-list` as indicated in the following example.
 
 ```html
-  <o-list  #list service="..." entity="..." keys="ID" keys-sql-types="UUID">
-      <o-list-item *ngFor="let list of list.dataArray">
-       ....
-      </o-list-item>
-    </o-list>
-```
\ No newline at end of file
+<o-list  #list service="..." entity="..." keys="ID" keys-sql-types="UUID">
+  <o-list-item *ngFor="let list of list.dataArray">
+     ....
+  </o-list-item>
+</o-list>
+```