packages/components/src/format/list.tsx (1)

12-16: Prefer a stable key over array index (Line 14).

Using the array index can cause state/DOM mismatches when items are inserted/reordered. If items are strings, prefer a stable key derived from the content (and include the index only as a fallback for duplicates).

♻️ Suggested tweak

-					return <Text key={index}>{item}, </Text>;
+					return <Text key={`${item}-${index}`}>{item}, </Text>;

packages/components/src/label/index.tsx (1)

8-10: Import ordering: external dependency import should come before internal import.

Per coding guidelines, import order should be: React first → external dependencies → @wcpos/* internal imports. The @rn-primitives/types import (external) is placed after the internal ../lib/utils import.

♻️ Suggested fix for import ordering

 import * as LabelPrimitive from '@rn-primitives/label';
 import * as Slot from '@rn-primitives/slot';
+import type { SlottablePressableProps } from '@rn-primitives/types';

 import { cn } from '../lib/utils';
-
-import type { SlottablePressableProps } from '@rn-primitives/types';

packages/components/src/format-number/format-number.tsx (1)

186-188: Consider adding explicit type annotation.

The val parameter has an implicit any type. Per coding guidelines, explicit types should be used instead of any.

♻️ Suggested fix

-	const formatInput = React.useCallback((val) => {
+	const formatInput = React.useCallback((val: string) => {
 		return val;
 	}, []);

packages/components/src/data-table/index.web.tsx (1)

87-89: Replace console.log with the logger library.

As per coding guidelines, use @wcpos/utils/logger instead of console.log for logging.

♻️ Proposed fix

Add the import at the top of the file:

import { getLogger } from '@wcpos/utils/logger';

const logger = getLogger(['wcpos', 'components', 'DataTable']);

Then replace the console.log:

 meta: {
   expanded$,
   expandedRef,
   onChange: (data: any) => {
-    console.log('onChange called without handler', data);
+    logger.warn('onChange called without handler', { context: { data } });
   },
   ...tableMeta,
 },

packages/core/src/screens/main/components/customer-select.tsx (2)

76-81: Consider expanding the useEffect comment to explain WHY.

The cleanup effect is a valid use case, but per coding guidelines, the comment should explain WHY it's necessary, not just WHAT it does. For example: "Clear the search when unmounting to prevent stale search state from persisting in the query when the component remounts."

---

100-100: Avoid using any type for the query parameter.

The query: any violates the coding guideline to not use any type. Use the return type from useQuery or define a proper interface for the query object.

♻️ Suggested fix

-export function CustomerList({ query, withGuest }: { query: any; withGuest: boolean }) {
+export function CustomerList({ query, withGuest }: { query: ReturnType<typeof useQuery>; withGuest: boolean }) {

Alternatively, if useQuery exports a specific type, import and use that instead.

As per coding guidelines: "Do not use 'any' type; use strict types and generics instead"