Replaced URL(path, apiUrl) with URL(`${apiUrl}/${path}`) to ensure the apiUrl's path segment is preserved during URL construction.
Why ❔
The existing code did not properly handle cases where the apiUrl includes a path (e.g., "https://.../api"). The original method of using URL(path, apiUrl) incorrectly stripped away the path segment (e.g., /api) from the apiUrl, leading to incorrect URLs. This change also enhances the codebase's consistency, as this method of constructing URLs is used in most other places.
What ❔
Replaced
URL(path, apiUrl)
withURL(`${apiUrl}/${path}`)
to ensure the apiUrl's path segment is preserved during URL construction.Why ❔
The existing code did not properly handle cases where the apiUrl includes a path (e.g., "https://.../api"). The original method of using
URL(path, apiUrl)
incorrectly stripped away the path segment (e.g.,/api
) from the apiUrl, leading to incorrect URLs. This change also enhances the codebase's consistency, as this method of constructing URLs is used in most other places.