Release v2.3.0

[gyaneshgouraw-okta]

Added

• Update Angular to Angular 18 #675 (frederikprijck)
• Incorporate observable of loginWithRedirect in observable returned by AuthGuard #660 (Mobe91)
• Add Skip the Auth0 login page to FAQ #661 (frederikprijck)

To fix this, ensure that C (an instance of t.FieldRef) is converted to a string explicitly when used as a key in object property access. The best way to achieve this is to use C.toString() or define a method on FieldRef that provides a unique string representation of the instance. Then, replace usages like r[C] and r[C] = ... with r[C.toString()] and r[C.toString()] = ... respectively, so that the property key is guaranteed to be a string.

You only need to edit the code in the region shown (lines 938–944 and 941–943 in particular). No additional imports are needed unless you are required to implement a custom toString() method on FieldRef, but you cannot add that unless it is present in the snippet.

---

To fix the problem, we need to make sure that property access in r[C] and property assignment r[C] = ... use an explicit string key, ideally one that uniquely identifies the FieldRef instance. This is typically done by adding a method (e.g., toString() or toKey()) to the FieldRef class that returns a string representation which uniquely identifies the instance (e.g., via concatenating its fields). All usages of r[C] should be replaced with r[C.toString()] or r[C.toKey()]. In the provided snippet, this affects both the property read (r[C]) and assignment (r[C] = ...).

Assuming we do not have code for the FieldRef class, and can only edit the provided file docs/assets/main.js, the best fix that does not break functionality is to change r[C] to r[C.toString()] at both the read (W = r[C]) and assignment (r[C] = ...) locations. If we see further property accesses with C as key, they should be similarly updated.

---

To fix this problem, simply remove the assignment to T at line 970 (T = t.FieldRef.fromString(C)). The variable C is the only variable needed for the purposes of the code in that loop, and since T is not used after assignment within that loop, its declaration and assignment are unnecessary. No other structures or imports are needed. Edits should be applied only to this loop, within docs/assets/main.js, for the lines shown.

---

To fix the problem, we should explicitly convert the FieldRef object to a string key when it is used as a property name. Instead of relying on JavaScript's implicit conversion (i.e., this.fieldLengths[y] = ...), we should write this.fieldLengths[y.toString()] = .... This makes the code more readable and maintainable, and prevents issues if the toString() implementation changes or if the class structure changes in the future. This explicit conversion should be applied in all instances within the given function where y (a FieldRef object) is being used as a property key: lines 1092, 1093, 1094.

Files/regions/lines to change:

• File: docs/assets/main.js
• Lines: 1092, 1093, 1094
  (this.fieldTermFrequencies[y], this.fieldLengths[y] = 0, this.fieldLengths[y] += d.length)
• For each, use y.toString() instead of y.

No new methods or imports are needed, assuming FieldRef.prototype.toString exists and is well-defined.

---

To fix this problem, we should explicitly convert the FieldRef object to a string when using it as a property key in JavaScript objects, to avoid accidental stringification to "[object Object]" and possible property name collisions. The ideal fix is to call a method like .toString() on y (the FieldRef instance), assuming it implements a suitable stringification method, or to construct a unique string from its distinguishing fields if not.

Specifically, in docs/assets/main.js, line 1094 and all other locations in the surrounding block where y is used as a key (i.e., keys into this.fieldTermFrequencies, this.fieldLengths, etc.), the usage should be changed from y to y.toString(). This requires that FieldRef implements a unique and stable .toString() method. If necessary, we should show how to add such a method using its fields (like ref and field). If we cannot add new methods (due to code constraints), we should inline the construction of a unique string in place.

Our changes are limited to the lines we've seen, so we'll update usages such as this.fieldTermFrequencies[y], this.fieldLengths[y], etc., to this.fieldTermFrequencies[y.toString()], and so on. No need to add imports; just use built-in functionality.

---

To resolve the problem, simply remove the redundant double quote character " from the character class in the regex on line 1927. The character class should contain each character only once. Since the mapping object He only cares about single quote and double quote individually, and the regex is used to escape those characters, keep only one instance of ". The replacement requires editing line 1927 in docs/assets/main.js to change /[&<>"'"]/g to /[&<>"']/g, with no change in behavior.

---

To fix this problem, we should remove the unnecessary initialization of the variable Be to !1 (false). Instead, simply declare the variable Be with var, and let its value be assigned only when needed in the relevant conditional. This has no effect on functionality, since all control paths either assign a value to Be based on the checked conditions or leave it as undefined or false as needed, and no usage occurs prior to assignment. Edit only the declaration of Be on line 1940 within docs/assets/main.js.

---

The best fix is to remove the unused assignment of Be = !0 on line 1948. Since the value assigned to Be is neither used nor read anywhere else in the shown code, omitting the assignment altogether is both safe and appropriate. This should be limited to the code region surrounding line 1948—only the assignment portion (not the surrounding logic for event type switching) should be edited. No imports, method definitions, or variable definitions need to be added or modified.

---

The best way to address this problem is to remove the useless conditional from the 'click' event listener — specifically, the if (pe) block at line 1966, since pe is always false in the code shown and the body will never execute. Remove the entire if (pe) block (lines 1966–1967), or (if it's required for structural reasons) simply remove the check and leave an empty event listener. There are no other dependencies, imports, or required method changes as this is a local fix. If in future functionality is planned that sets pe to true elsewhere, then that functionality should be implemented before restoring this block.

---