moar release fixes #2471

Merged
tzarebczan merged 8 commits from fix-mature-checkbox into master 2019-05-10 17:10:56 +02:00
tzarebczan commented 2019-05-10 01:27:29 +02:00 (Migrated from github.com)

Fixes claim editing while keeping any existing tags + setting/clearing fee.
Fixes not being able to abandon claims if file was deleted

Beware of lint errors..some old and new. Everything works and we should clean them up later once tags are properly integrated.

Fixes claim editing while keeping any existing tags + setting/clearing fee. Fixes not being able to abandon claims if file was deleted Beware of lint errors..some old and new. Everything works and we should clean them up later once tags are properly integrated.
neb-b (Migrated from github.com) requested changes 2019-05-10 07:18:56 +02:00
neb-b (Migrated from github.com) left a comment

Minor comments

Minor comments
neb-b (Migrated from github.com) commented 2019-05-10 07:13:41 +02:00

This should just be fee

Because if fee is undefined, it will error when trying to read amount

This should just be `fee` Because if `fee` is undefined, it will error when trying to read `amount`
neb-b (Migrated from github.com) commented 2019-05-10 07:15:43 +02:00

This might be a little more readable:

const [txid, nout] = outpoint.split(':')
This might be a little more readable: ``` const [txid, nout] = outpoint.split(':') ```
@ -217,2 +219,3 @@
fee?: { amount: string, currency: string },
tags: Array<string>,
locations?: Array<Location>,
license_url?: string,
neb-b (Migrated from github.com) commented 2019-05-10 07:18:20 +02:00
tags: claim && claim.value.tags || []

so we don't have to check that tags exitsts inside publishPayload

``` tags: claim && claim.value.tags || [] ``` so we don't have to check that `tags` exitsts inside `publishPayload`
neb-b (Migrated from github.com) commented 2019-05-10 07:18:44 +02:00

We shouldn't need to check that publishPayload.tags exists here

We shouldn't need to check that `publishPayload.tags` exists here
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#2471
No description provided.