Closes #1302

Test that your selection for preferred is remembered in local storage.

1. Set it to on
2. Tab over to wallet or another page
3. Refresh
4. Visit discovery - it should have remembered the state was on.
5. Turn it off, and repeat to confirm that is remembers the 'off' state

added scoped labels

added scoped label and automatically removed label

This is now no longer defaulting to preferred by default.

added 1 commit

• 15db3ac9 - Default to true

Compare with previous version

added scoped label and automatically removed label

Still issues here @benhayward.ben.

The XHR request is returning preferred when it should be all.

added scoped label and automatically removed label

Looked into this today, that bug is present on production also; and furthermore, this is happening (which it is not in this MR) #2240 (closed)

Thats seems to be a different issue. Here you have 'preferred' set to off, but you are not passing all=1. There is not subsequent XHR request to be made.

added 90 commits

• 15db3ac9...6ad11c19 - 86 commits from branch master
• 57a897da - Merge branch 'master' of gitlab.com:minds/front into feat/default-disc-tags-1366
• fd50b273 - Merge branch 'master' of gitlab.com:minds/front into feat/default-disc-tags-1366
• 77f61c90 - Merge branch 'master' of gitlab.com:minds/front into feat/default-disc-tags-1366
• ca24fc35 - Fixed issue with all not being respected

Compare with previous version

added 1 commit

• eb4110bd - Minor change

Compare with previous version

added 1 commit

• d2ba1e1b - Switching default value to off

Compare with previous version

approved this merge request

assigned to @xander-miller

assigned to @edgebal

Issue detected by @markeharding is still present. When you disable preferred state, navigate away, and then back. The URL on the browser lacks the ;all=1 part which is what the component uses to know if it should fetch the complete result set.

assigned to @benhayward.ben

Follow up: XHR is fetching the results correctly (&all=X is being correctly set). Only the permalink is missing the ;all=1 fragment.