Onboarding updates #197
No reviewers
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
Invalid
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-redux#197
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "onboarding"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Changes
myChannelClaims
now defaults toundefined
. This is helpful to know if we've fetched a users channel claims or not.undefined
=== not fetched,null
=== fetched and no channelssync
file here. I'm not sure if it belongs here but I think it makes sense to handle the data (after it's been fetched by some service) to populate our reducers inlbry-redux
. If everything is inlbryinc
we need to either import a constant fromlbryinc
intolbry-redux
or just hard-code theACTIONS.POPULATE_USER_SETTINGS
action.replace settings with shared user state, shared state, or something else
why undefined though?
if Sets have issues, just make it an object and use the keys, it's basically the same thing
@ -68,0 +74,4 @@
...state,
followedTags: tags && tags.length ? tags : DEFAULT_FOLLOWED_TAGS,
};
},
when receiving saved/stored user state, I think it's probably fine (and possible better) to overwrite than to try to merge
...I may be misunderstanding what this function is doing
this should probably be
return []
;So we can track if we've fetched a users channels. If it's undefined, we haven't fetched them yet.
It's returning undefined so we can check in the app if we've ever fetched before.
@seanyesmunt I merged the latest commit with the master branch in order to get the changes that I merged from the
channel-creator
branch in. If this causes any problems, please feel free to revert. Thanks.For this, I don't think we should override with
DEFAULT_FOLLOWED_TAGS
if no tags are returned by the remote saved state. That may override the local state if the user has made any changes, or in cases where the shared state may have ended up out of sync.@ -0,0 +10,4 @@
};
function extractUserState(rawObj: v0Data) {
if (rawObj && rawObj.version === '0.1' && rawObj.shared) {
Should we be checking for version here? That means we'll probably have to update this with every new version, but I suppose it's not too big of a deal since we'll eventually transition to sync using the wallet servers.
@ -0,0 +10,4 @@
};
function extractUserState(rawObj: v0Data) {
if (rawObj && rawObj.version === '0.1' && rawObj.shared) {
I think so. With new versions we would have to update anyway since that would probably mean changing the shape of persisted object.
Maybe
if (!followedTags && !tags) return DEFAULT_FOLLOWED)TAGS
else return tags
?
@akinwale I'm going to merge this just so it's easier to work with. We can continue to make changes to it.