Service #10
Service #10
Conversation
| let response = await fetch(this.props.serviceUrl) | ||
| let data: string = await response.text() | ||
|
|
||
| // Match any number of characters between <head> tags. Case-insensitive, including newline | ||
| let headContentRegex = /<head>(.*)<\/head>/is | ||
| let matches: RegExpExecArray | null = headContentRegex.exec(data) | ||
|
|
||
| let headContent = "" | ||
|
|
||
| if (matches && matches.length > 0) { | ||
| headContent = matches[1] | ||
| } | ||
|
|
||
| if (!headContent) return "" | ||
|
|
||
| /// Matches THE FIRST <link> tag whose [rel] property contains "icon" and extracts the url WITHOUT the domain | ||
| let faviconRegex = /<link.*rel=".*icon.*".*href="(.+)".*>/i | ||
| matches = faviconRegex.exec(headContent) | ||
|
|
||
| let faviconUrl = "" | ||
|
|
||
| if (matches && matches.length > 0) { | ||
| faviconUrl = `${this.props.serviceUrl}${matches[1]}` | ||
| } |
There was a problem hiding this comment.
Google offers a Favicon Snatcher service, by simply fetching
https://www.google.com/s2/favicons?domain=URL
we obtain the favicon of the desired website, this would greatly simplify the process.
Note:
Using Google's service we do not obtain the link to the favicon but the image itself
There was a problem hiding this comment.
I'll check out this API and see if I can use it
There was a problem hiding this comment.
I checked on that API and I found out that Google never intended to distribute that endpoint but it was for internal use only. so it's not safe to use it because they can lock it anytime.
Another option could be https://rapidapi.com/rubycuts/api/grabicon but it's latency times are way too long, at least trying on their example page.
Yeah, nice point. I'm going to remove package-lock.json |
|
I just made a refactor of service.tsx, now it is a fnc, also i made a rebase into the origin develop since there were many changes |
|
@JEToP/hacktoberfest-front-end This service is actually a container of functions that will be useful in the future, IDK if merge it or not |
|
Those functions are needed only in the Service Component, maybe we could just merge it and wait for the UI part to render it |
Added Service Component
Added basic checks for props (I just check if some fields are empty because passwords from different websites can have different restrictions, also the username can be either a nickname or a password)
Added function to fetch favicon from any website that uses it within a 'link' tag, yet to add other kind of favicons
Added base structure to make the actual POST request on the DB, Endpoint is missing and keys for the data to be sent need to be edited in the future to match the correct properties