Aman-Mittal opened a new issue, #486: URL: https://github.com/apache/fineract-backoffice-ui/issues/486
## What happens A `TypeError` is caught and logged twice on every single route load: ``` [log] Initializing API BASE_PATH: https://sandbox.mifos.community/fineract-provider/api/v1 [log] e TypeError: Failed to construct 'URL': Invalid base URL [warn] [Ionicons Warning]: Could not load icon with name "flash-outline". ... [log] e TypeError: Failed to construct 'URL': Invalid base URL [warn] [Ionicons Warning]: Could not load icon with name "checkmark-done-outline". ... ``` The pairing is exact and repeatable: **one `Invalid base URL` immediately before each Ionicons warning**, two of each, every load. That strongly suggests the icon-loading path constructs a `URL` from a bad or relative base, throws, and only then falls back to the failing name-based lookup — i.e. this exception is the upstream cause of the two icons that never render (filed separately). Nothing surfaces to the user. The exception is swallowed and logged, so the only symptom is a permanently noisy console. ## Why it is worth fixing beyond the noise Combined with the two Ionicons warnings and the two `branding/*` 404s (also filed separately), a developer opening DevTools on this app sees **six recurring console entries on every page load before doing anything at all**. That is enough noise that a genuine new error is easy to miss, which is the practical cost here. ## What to look at The `URL` construction happens in the icon-resolution path — the throw sits between `Initializing API BASE_PATH` and the Ionicons warning on every load. A base of `''`, `undefined`, or a relative path passed as the second argument to `new URL(...)` produces exactly this message. Registering icons explicitly via `addIcons` would likely remove the lazy-resolution path entirely and take this exception with it. ## Environment Reproduced against a clean checkout of `main` (`a24a06ba`) served with `ng serve`, backend `sandbox.mifos.community`, Chrome. Present on `/dashboard`, `/clients`, `/clients/create` and every other route checked; survives a hard reload with cache disabled. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
