Description
Currently, PearPass extracts service icons using only the root domain or subdomain. However, I have multiple different services hosted on subpaths of the same domain, for example domain.com/service1 and domain.com/service2. Right now, they all get the same root domain icon, making it hard to distinguish them visually.
Proposed Solution
Update the favicon fetching logic to use the full provided URL path instead of stripping it down to the domain. This will allow the app to fetch the correct unique favicon for services hosted on subpaths.
Description
Currently, PearPass extracts service icons using only the root domain or subdomain. However, I have multiple different services hosted on subpaths of the same domain, for example domain.com/service1 and domain.com/service2. Right now, they all get the same root domain icon, making it hard to distinguish them visually.
Proposed Solution
Update the favicon fetching logic to use the full provided URL path instead of stripping it down to the domain. This will allow the app to fetch the correct unique favicon for services hosted on subpaths.