Skip to content
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

Discovery user refresh bug 🐜 #476

Merged
merged 1 commit into from
Feb 13, 2019
Merged

Discovery user refresh bug 🐜 #476

merged 1 commit into from
Feb 13, 2019

Conversation

eoji
Copy link
Contributor

@eoji eoji commented Feb 12, 2019

What ❓

I was going to open another PR but then I noticed, if you're logged in, looking at a category in Discovery and you leave that screen, Discovery shows the default params (recommended if you’re opted in or all projects). This PR fixes the bug that causes Discovery to show default params every time currentUser emits. We really only care if the user changes (shoutout to my friend changedUser #224).

How to QA? 🤔

In Discovery, view a category or top filter that's not your default. Trigger a user refresh; you can open up settings or open up a different app. When you return, you should see the category/top filter you previously chose.

currently in prod

device-2019-02-12-160236 2019-02-12 16_05_47

the fix

device-2019-02-12-160354 2019-02-12 16_05_42

…rrentUser` emitted. We really only care if the user changes.
@eoji eoji added the bug 🐛 label Feb 12, 2019
@eoji eoji requested a review from Rcureton February 12, 2019 21:11
Copy link
Contributor

@Rcureton Rcureton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great bug fix 🎉

✅Tested

  • Tested on the Samsung s8

@eoji eoji merged commit 624e7d0 into master Feb 13, 2019
@eoji eoji deleted the io/disco-params-bug branch February 13, 2019 15:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants