@igamingcareer/igaming-components 1.1.15 → 1.1.17

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/Readme.md CHANGED
@@ -124,6 +124,43 @@ export function Example() {
124
124
  }
125
125
  ```
126
126
 
127
+ ## JobsList filter configuration
128
+
129
+ `JobsList` now supports multi-select company/country/city filters, optional counts in filter labels, and top-level sorting for those filter options.
130
+
131
+ ```tsx
132
+ <JobsList
133
+ apiUrl={process.env.NEXT_PUBLIC_JOB_API_URL!}
134
+ filterKeys={["company", "country", "city", "department"]}
135
+ searchableFilters={["company", "country", "city", "department"]}
136
+ filterDisplayConfig={{
137
+ multiSelectKeys: ["company", "country", "city"], // default
138
+ showOptionCounts: true, // default, renders "Malta (3)"
139
+ optionSort: "count_desc", // "alphabetical" | "count_desc" | "count_asc"
140
+ }}
141
+ />
142
+ ```
143
+
144
+ ### `filterDisplayConfig`
145
+
146
+ - `multiSelectKeys`
147
+ - Controls which dynamic filters render as multi-select checkbox groups.
148
+ - Defaults to `["company", "country", "city"]`.
149
+ - If you remove one of those keys, that filter falls back to the legacy single-select dropdown.
150
+
151
+ - `showOptionCounts`
152
+ - Defaults to `true`.
153
+ - When `true`, dynamic filters show the number of matching jobs next to each option.
154
+ - Example: `Malta (3)`.
155
+ - Set it to `false` only if you want to hide those counts.
156
+
157
+ - `optionSort`
158
+ - Controls how dynamic filter options are ordered.
159
+ - Supported values:
160
+ - `"alphabetical"` (default)
161
+ - `"count_desc"` — highest count first
162
+ - `"count_asc"` — lowest count first
163
+
127
164
  ## Login (remember me identifier)
128
165
 
129
166
  The `Login` and `LoginForm` components support a real “Remember me” experience by persisting the identifier (email/username)