Hey there, back again with another pre-release version of Thunder for v0.2.1+9! This will probably be the final list of new features that are going to be added in the upcoming release, so it will just be bug fixing major things that pop up here and there.
Note: There is currently a login issue with lemmy.world due to the upgrade to 0.18.1. This is not something on Thunder’s end
Be fully prepared to know that these pre-release versions may contain major bugs which could cause Thunder to crash or behave unexpectedly.
Without further ado, these are the changes from last time:
- Added ability to edit your own comments, the action simple replaces the reply swipe action when on your own comment
- Fixed an issue where performing vote/save actions on comments would do it to the first comment in the thread (the parent one)
- Fixed issue where subscribing from the search page would cause an error to pop up
- Fixed issue where setting a default sort option would cause infinite loading to happen
For things to test out, I would suggest just testing out general things like voting, saving, replying, and creating posts, as well as testing out the following things (these are issues which are marked as “fixed” in the issues tab)
- Error when subscribing from community search #160
- Display vote counts for posts #159
- Ability to edit comments #158
- Upvote and downvote buttons feel unresponsive #141
- Increase visual separation of posts in dark theme #137
- Timeouts replace entire screen with error message #134
- Reply button covers text #130
- Unable to exit #124
- Mark as read button on read inbox messages is not functional #121
- Pull to refresh doesn’t work on posts #120
- Alternate comment collapse behaviour #119
- Inconsistent haptic feedback when upvoting with gestures # 116
- Add share button to post in list view #106
- Sort by top #101
- Media download button #50
- Stuttering issues while scrolling #24
- Simple way to access a user or community profile #17
The scroll-to-comment feature hasnt been implemented yet! You can definitely create a new issue on GitHub for it so that it’s easier for me to track :D