-
-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Redirect opensauced.pizza/username to /user/username #124
Comments
Yes. This will most likely need an edge function to quickly check if the user exist in the API. Open to other suggestions. |
@bdougie Where would the user be redirected if the user doesn't exist? Since we are redirecting users to the insight, shouldn't the insight app handle the rest? |
Correct ideally the insights app would have a 404. Today the page displays with errored data if not found. |
Might be better suited for a URL shortener. |
@bdougie If we use the "/username" path we will be required to check our existing pages ('/blog', '/teams) and add some logic to treat these as reserved paths. And this has to be refactored every time we add a new route for pages. But if we use "/u/username" we will not be required the checking. Which path should we go for? |
Let's go with /u |
Type of feature
🍕 Feature
Current behavior
Working on social cards and it would be nice to redirect these urls.
Suggested solution
Add a redirect in Netlify
Additional context
No response
Code of Conduct
Contributing Docs
The text was updated successfully, but these errors were encountered: