Comment replies ordered from newest to oldest (top-down) #948

New issue

Open

opened 2020-06-26 04:57:20 +02:00 by clay53 · 0 comments

clay53 commented 2020-06-26 04:57:20 +02:00 (Migrated from github.com)

Copy link

The Issue

Steps to reproduce

1. Go to a video with comments that have replies
2. Scroll down to comments with replies
3. Look and be slightly confused

Expected behaviour

The comments should be ordered oldest to newest

Actual behaviour

The comments are ordered newest to oldest

System Configuration

• Device: Samsung Galaxy S7
• Android version: 8.1

Screenshots

Acceptance Criteria

1. Replies are ordered from oldest to newest (top-down)

Definition of Done

• Tested against acceptance criteria
• Tested against the assumptions of the user story
• The project builds without errors
• Unit tests are written and passing
• Tests on devices/browsers listed in the issue have passed
• QA performed & issues resolved
• Refactoring completed
• Any configuration or build changes documented
• Documentation updated
• Peer Code Review performed

<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. We are also available on live chat at https://chat.lbry.com --> ## The Issue ### Steps to reproduce 1. Go to a video with comments that have replies 2. Scroll down to comments with replies 3. Look and be slightly confused ### Expected behaviour The comments should be ordered oldest to newest ### Actual behaviour The comments are ordered newest to oldest ## System Configuration - Device: Samsung Galaxy S7 - Android version: 8.1 ## Screenshots <!-- If a screenshot would help explain the bug, please include one or two here -->  ### Acceptance Criteria 1. Replies are ordered from oldest to newest (top-down) ### Definition of Done - [ ] Tested against acceptance criteria - [ ] Tested against the assumptions of the user story - [ ] The project builds without errors - [ ] Unit tests are written and passing - [ ] Tests on devices/browsers listed in the issue have passed - [ ] QA performed & issues resolved - [ ] Refactoring completed - [ ] Any configuration or build changes documented - [ ] Documentation updated - [ ] Peer Code Review performed

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

dep-update

test-deploy

notification-debugging

commenting

crash-fixes

user-bugs

unlock-tips

reward-drivers

visual-tweaks

dark-theme-fix

fullscreen-on-rotate

native-rewrite

0.17.1

0.17.0

0.16.14

0.16.13

0.16.12

0.16.11

0.16.10

0.16.9

0.16.8

0.16.7

0.16.6

0.16.5

0.16.4

0.16.3

0.16.2

0.16.1

0.16.0

0.15.16

0.15.15

0.15.14

0.15.13

0.15.12

0.15.11

0.15.10

0.15.9

0.15.8

0.15.7

0.15.6

0.15.5

0.15.4

0.15.3

0.15.2

0.15.1

0.14.3

0.15.0

0.14.2

0.14.1

0.14.0

0.13.4

0.13.3

0.13.2

0.13.1

0.13.0

0.12.3

0.12.2

0.12.1

0.12.0

0.11.1

0.11.0

0.10.2

0.10.1

0.10.0

0.9.3

0.9.2

0.9.1

0.9.0

0.8.4

0.8.3

0.8.2

0.8.1

0.8.0

0.7.5

0.7.4

0.7.3

0.7.2

0.7.1

0.7.0

0.6.2

0.6.1

0.6.0

0.5.0

0.4.0

0.3.1

0.3.0

0.2.3

0.2.2

0.2.1

0.2.0

0.1.10

0.1.9

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

Labels

Clear labels   

android: closed alpha

  

android: open beta

  

app-parity

  

area: devops

  

area: discovery

  

area: docs

  

area: livestream

  

area: proposal

Work is part of a proposal

  

consider soon

Discuss this issue at the next planning meeting, then remove this label

  

creator

  

Epic

  

good first issue

  

hacktoberfest

Welcome to Hacktoberfest

  

help wanted

  

icebox

Long-term storage

  

Invalid

  

level: 1

No knowledge of the existing code required

  

level: 2

Some knowledge of the existing code is recommended

  

level: 3

Significant knowledge of the existing code is recommended

  

level: 4

Intimate knowledge of the existing code is recommended

  

needs: exploration

Solution unclear, needs research

  

needs: grooming

Issue needs to be groomed before work can start

  

needs: priority

Priority level needs to be defined

  

needs: repro

Issue needs step-by-step instructions on how to reproduce in latest code

  

needs: tech design

Needs technical design signoff before implementation can begin

  

on hold

Temporarily paused

  

priority: blocker

Issue is blocking release, do ASAP

  

priority: high

Work needs to be moved into sprint ASAP

  

priority: low

Work should be done but can stay in the backlog for now

  

priority: medium

Work needs to be done within 2-3 sprints

  

product review

  

resilience

  

Tom's Wishlist

  

type: bug

Existing functionality is wrong or broken

  

type: discussion

A conversation. No specific changes requested

  

type: improvement

Existing (or partially existing) functionality needs to be changed

  

type: new feature

New functionality that does not exist yet

  

type: refactor

Minimal user-visible changes, but significant internal work

  

type: task

Either work that's not related to the code, or a small chore that does not fit into other categories

  

type: testing

Solution needs additional user testing

  

unplanned

Work that was not planned into the spirnt, took priority over planned work

No labels

android: closed alpha

android: open beta

app-parity

area: devops

area: discovery

area: docs

area: livestream

area: proposal

consider soon

creator

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

product review

resilience

Tom's Wishlist

type: bug

type: discussion

type: improvement

type: new feature

type: refactor

type: task

type: testing

unplanned

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

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-android#948

No description provided.