Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 month ago

URL-shortening-API-landing-page

react-native, tailwind-css
WANYIKE•170
@wanyike
A solution to the URL shortening API landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

All the feed back are welcomed thanks in advance.

What challenges did you encounter, and how did you overcome them?

The API refused to work I need help APIS mine is not working I will be happy when my humble request is accepted. submitting react native project also was a challenge for me.

What specific areas of your project would you like help with?

APIS area

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Thomas TS•1,270
    @ttsoares
    Posted about 1 month ago

    This is how I did it some time ago:

    var urlNoProtocol = url.replace(/^https?\:\/\//i, "");
    const response = await fetch(`https://api.shrtco.de/v2/shorten?url=${urlNoProtocol}`);
    const data = await response.json();
    

    The 'url' variable has what the user wrote in the form.

    What do that Regular Expression ?

    • Removes the "http://" or "https://" part from the URL, in a case-insensitive manner.
    • It does this by matching the "http://" or "https://" at the beginning of the string (^).
    • The "?" after the "s" makes the match for "s" optional, so both "http" and "https" are matched.
    • The "i" flag at the end makes the match case-insensitive.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub