packages/components/src/virtualized-list/virtualized-list.tsx (1)

83-87: Consider adding type annotation for children parameter.

The Item component's children parameter lacks a type annotation. While this is pre-existing code, it conflicts with the project's strict typing guideline.

♻️ Suggested type annotation

-function Item({ children }) {
+function Item({ children }: { children: React.ReactNode }) {
 	// const { item, index } = useItemContext();
 
 	return <>{children}</>;
 }

Also, the commented-out code could be removed if it's no longer needed.

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

12-15: Prefer a stable key over index to avoid reorder bugs.
If array can reorder or have insertions/removals, using index can cause state mismatches. Since items are strings, prefer item (or \${item}-${index}`` if duplicates are possible).

Proposed change

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

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

100-100: Consider replacing any with a proper type.

The query parameter uses any, which violates the coding guideline to use strict types. Since useQuery is from @wcpos/query, consider typing it properly.

♻️ Suggested improvement

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

Or define a dedicated type/interface for the query object if ReturnType<typeof useQuery> is too verbose.

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

packages/query/src/use-relational-query.ts (1)

91-105: Consider clarifying the ESLint disable comment.

The comment on line 103 only mentions parentIdentityKey, but the re-registration logic is also affected by childIdentityKey (transitively through registerQueries). While functionally correct, updating the comment to reference both identity keys would improve clarity.

📝 Suggested comment update

-		// eslint-disable-next-line react-hooks/exhaustive-deps -- parentIdentityKey triggers re-registration when query identity changes
+		// eslint-disable-next-line react-hooks/exhaustive-deps -- identity keys trigger re-registration when query identity changes (childIdentityKey via registerQueries)

packages/components/src/command/index.tsx (2)

61-72: Avoid using any type for the scroll event parameter.

The event: any violates the coding guidelines. Consider using the proper React Native type for scroll events.

♻️ Suggested fix

+import { Pressable, ScrollView, Text, View, NativeScrollEvent, NativeSyntheticEvent } from 'react-native';
...
 	const handleScroll = React.useCallback(
-		(event: any) => {
+		(event: NativeSyntheticEvent<NativeScrollEvent>) => {
 			const { layoutMeasurement, contentOffset, contentSize } = event.nativeEvent;

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

---

107-109: Replace hardcoded color with semantic color class.

The hardcoded backgroundColor: '#e5e7eb' and inline style violate the styling guidelines. Consider using a semantic color class via className for theme compatibility.

♻️ Suggested fix

 const CommandSeparator = React.forwardRef<View, CommandSeparatorProps>((props, ref) => (
-	<View ref={ref} style={[{ height: 1, backgroundColor: '#e5e7eb' }]} {...props} />
+	<View ref={ref} className="h-px bg-muted" {...props} />
 ));

As per coding guidelines: "Always prefer semantic color classes (bg-background, bg-card, bg-sidebar, bg-muted, bg-table-header) over hardcoded colors" and "Prefer className over inline styles".

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

186-188: Add explicit type annotation for val parameter.

The val parameter has an implicit any type, which violates the coding guideline to use strict types. As per coding guidelines: "Do not use 'any' type; use strict types and generics instead."

♻️ Proposed fix

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

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

98-99: Replace console.log with logger.

Per coding guidelines, use the logger library exclusively for logging instead of console.log.

Suggested fix

+import log from '@wcpos/utils/logger';

 onChange: (data: any) => {
-	console.log('onChange called without handler', data);
+	log.warn('onChange called without handler', data);
 },

As per coding guidelines: "Use the logger library exclusively for logging; DO NOT use console.log. Import: import log from '@wcpos/utils/logger'"

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

87-88: Replace console.log with logger.

Same issue as in index.tsx - per coding guidelines, use the logger library instead of console.log.

Suggested fix

+import log from '@wcpos/utils/logger';

 onChange: (data: any) => {
-	console.log('onChange called without handler', data);
+	log.warn('onChange called without handler', data);
 },

As per coding guidelines: "Use the logger library exclusively for logging; DO NOT use console.log. Import: import log from '@wcpos/utils/logger'"

packages/core/src/utils/merge-stores.ts (1)

41-41: Avoid using any type.

The [key: string]: any index signature violates the coding guideline to use strict types instead of any. Consider defining a proper interface for the store object or using unknown with type guards.

♻️ Suggested improvement

-	remoteStores: { id: number; [key: string]: any }[];
+	remoteStores: { id: number; [key: string]: unknown }[];

Or better, define a dedicated type:

interface RemoteStore {
	id: number;
	name?: string;
	// ... other known properties
}

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

packages/query/src/hooks/categories.tsx (2)

1-8: Consider renaming file extension from .tsx to .ts.

This file contains no JSX or React code—only a pure utility function. Using the .tsx extension is unnecessary and could be misleading. Consider renaming to categories.ts for consistency.

---

1-3: Empty JSDoc comment provides no value.

The JSDoc block is empty and doesn't document anything useful. Either add meaningful documentation or remove it.

♻️ Suggested fix

-/**
- *
- */
 const filterApiQueryParams = (params: Record<string, unknown>) => {

Or add useful documentation:

-/**
- *
- */
+/**
+ * Filters API query parameters before sending to the WooCommerce API.
+ * `@param` params - The query parameters to filter
+ * `@returns` The filtered parameters
+ */
 const filterApiQueryParams = (params: Record<string, unknown>) => {

packages/core/src/screens/main/components/header/user-menu.tsx (1)

103-103: Consider using a semantic color class for the hover state.

hover:bg-white/10 is a hardcoded color that may not adapt well to all themes. As per coding guidelines, prefer semantic color classes to ensure theme compatibility.