fix: The "Max _N_ items retrieved" message in c-select now accounts f…

…or list calls that don't provide a count, e.g. by passing `noCount=true`.

CHANGELOG.md

@@ -1,3 +1,7 @@
+# 5.0.4
+
+- fix: The "Max _N_ items retrieved" message in c-select now accounts for list calls that don't provide a count, e.g. by passing `noCount=true`.
+
 # 5.0.3
 
 - fix: Remove flawed logic that chooses the wrong foreign key for navigation properties where the target type of the navigation property has a primary key that also serves as a foreign key in some other relationship. In exceedingly rare cases, you may now have to add a `[ForeignKey(Name = ...)]` attribute to any navigation properties that may now throw a codegen validation error that their foreign key property cannot be discovered automatically. Related to this issue, `ClassViewModel.IsOneToOne` is now deprecated and slated for future removal.

src/coalesce-vue-vuetify3/src/components/input/c-select.vue

@@ -166,7 +166,14 @@
           <!-- TODO: With this version of c-select (versus the v2 one),
         we can implement infinite scroll much easier. Consider doing this instead of having this message. -->
           <v-list-item
-            v-if="listCaller.pageCount && listCaller.pageCount > 1"
+            v-if="
+              // When we do know an actual page count:
+              (listCaller.pageCount && listCaller.pageCount > 1) ||
+              // When `noCount` is used or counting is disabled on the server:
+              (listCaller.pageCount == -1 &&
+                listCaller.pageSize &&
+                listItems.length >= listCaller.pageSize)
+            "
             class="text-grey font-italic"
           >
             Max {{ listCaller.pageSize }} items retrieved. Refine your search to