@ieeesa-npm/groups 0.15.13 → 0.15.14

package/lib/components/org-multi-select/org-multi-select.component.d.ts

@@ -164,6 +164,31 @@ export declare class OrgMultiSelectComponent implements OnInit, OnDestroy {
      * @memberof OrgMultiSelectComponent
      */
     isSelected(option: SelectOption): boolean;
+    /**
+     * Identity check shared by isSelected / toggleOption / removeOption so all
+     * three agree on what "the same option" means.
+     *
+     * Why not a strict id === id && name === name match: SelectOption.id is
+     * `number | string`, and the two sides being compared do not always carry the
+     * same representation of the same organization. A freshly searched API result
+     * can arrive with a numeric id while the already-selected value (from edit
+     * prefill, or a previous search) holds the string form of that same id, so a
+     * strict === misses them. Free-text chips are added with an empty id
+     * (see addTypedValue), so when the same name later comes back from the API
+     * with a real id there is no id to match on at all. Both cases made the
+     * dropdown checkbox render unchecked for an option that is in fact selected.
+     *
+     * Rule:
+     *  - If BOTH sides have a non-empty id, match by String(id) === String(id)
+     *    (number-vs-string safe).
+     *  - Otherwise (either side is a free-text chip with no id) fall back to a
+     *    trimmed, case-insensitive name match.
+     * @param {SelectOption} a -first option.
+     * @param {SelectOption} b -second option.
+     * @return {boolean} true when both refer to the same organization.
+     * @memberof OrgMultiSelectComponent
+     */
+    private isSameOption;
     /**
      * Removes a selected chip.
      * @param {SelectOption} option -the option to remove.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ieeesa-npm/groups",
-  "version": "0.15.13",
+  "version": "0.15.14",
   "peerDependencies": {
     "@angular/common": "^16.1.0",
     "@angular/core": "^16.1.0"