fixes blank tiles due to unsupported content #755
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
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
Osprey
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
resilience
Tom's Wishlist
type: bug
type: discussion
type: error handling
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/spee.ch#755
Loading…
Reference in a new issue
No description provided.
Delete branch "pagination"
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?
This is a draft of a solution.
What I'd like to do is have a central list of supported type strings ( 'image/jpg' ); passing this list allows for future filtering. Would it be better for supported types be passed or require()d?
Also, this function could be renamed or duplicated to GetAllMatchingChannelClaims, GetAllSupportedChannelClaims, or just GetChannelClaims. I don't think it makes sense to duplicate it just to get at currently unsupported content.
@ -68,15 +68,35 @@ export default (db, table, sequelize) => ({
});
},
This needs to be optional, chainquery functions should not be opinionated on Spee.ch content types.
@ -77,2 +73,2 @@
{ bid_state: 'Accepted' },
],
const defaultWhereClauses = {
See here and the original signature of
getAllChannelClaims: async (channelClaimId, bidState)
, this allows all claims to be fetched. The changes break this pattern and force Spee.ch filtering on code that should be unopinionated.@ -77,2 +73,2 @@
{ bid_state: 'Accepted' },
],
const defaultWhereClauses = {
I had read that once you go beyond 1 optional parameter, you're better off passing an object. With bidState already being optional and not passed from the controller, contentTypes would have to be a second optional parameter, meaning the function, I think, would have to be called with ( first, null, third ). Is there a better way to make contentTypes optional? I'm leading toward a GetMatchingChannelClaims function in chainquery instead. This would pave the way for future db queries.
Merging to get a fix in ASAP, will make a clean-up task.