-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
fix(ui) Remove initial redirect logic from frontend #8401
fix(ui) Remove initial redirect logic from frontend #8401
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought the idea was to support filtering for specific pages to save redirect link for? That is another idea to avoid removing this altogether. For example, if you're editing a doc and did not save it it's really useful to come back to that context.
Basically, are we throwing the baby out with the bathwater here. Is there any reason to believe in the future that having this logic already there would be helpful? Or if your thinking that we'd dig this out of git history at that point if we feel it's really necessary? |
@jjoyce0510 thinking we pull this out of git if we want it back! otherwise it's just confusing to leave an unused hook in there if you ask me |
also I didn't realize this - I thought the thinking was just to remove this for now and if we really want to we can add it back later? tbh all i've heard about this feature is confusion and negativity |
While this functionality may be useful to some, the majority of feedback we've heard around our redirect logic when first going to datahub is that it's unexpected and undesirable. This PR removes that logic so when you go to the homepage for the first time, that's all that happens (no redirect).
This also fixes a little type in our demo banner.
Checklist