Since this release doesn't hinge on any big task's completion, there is nothing stopping me from doing releases after completing a number of small tasks.
Each change is aimed at improving the user experience. Thus getting these changes out as quickly as possible is important. There's no reason to prolong the end user's suffering from a less polished experience.

As always please feel free to provide any feedback/bug reports in the comments.

Full changelog

v1.33.5

Auto-clear notifications if user looks at inbox screen.
Updated the UI of the community info screen.
Fixed a bug where the FAB button would be in the wrong spot if the keyboard is opened and closed.
Fixed some minor bugs when searching for communities.
Fixed a bug where image previews are blurry.
Fixed some image viewer bugs.

v1.33.4

Mention suggestions. When creating a post or comment, mentions (starting with ! or @) will show suggestions based what is typed.
Changed long tap on an image in the post list to open the image options menu. Previously it would preview the image full screen. This change was made to make long tapping more consistent (long tapping things usually opens a context menu).
Image preview redesign. Move buttons to the bottom of the screen for easier access. Translucent UI. UI auto hides on zoom.
Fixed a bug with the layout "Large list" where images would be clipped on the sides.
Fixed a bug where tapping "Share image" will cause the share sheet to show up constantly.

v1.33.3

Rework the community options menu. Organized and updated the options shown.
Added subscribe/unsubscribe as an action to the community options menu & link menu (for communities).
Added a solid background color to community and profile icons so they don't look odd when placed in front of a banner.
Added undo button to save post/comment snackbar.
Fixed some snack bar layout issues.

v1.33.2

This is equivalent to release v1.33.1. It's unique to the Github release and was done to address a build issue.

v1.33.1

Fixed two rare-ish crashes.
Overhauled the community navigation logic. This should hopefully eliminate more navigation bugs.

v1.33.0

Update message layout on the inbox screen to clearly indicate the sender and receiver.
Better blocking experience. Blocking a user/community or instance should now show a snackbar when the action completes with a button to undo.
Link menu enhancements. Long tapping "links" (eg. user name) will show more rich options that are specific to the link type. For instance long tapping a community link will show community options as well as link options.
Removed setting "sharing images directly". Due to the link menu enhancements, the setting for "sharing images directly" is now obsolete because both options are always present for images.
Fixed a bug where WEBM videos will not play.
Fixed some weird navigation bugs.

you are viewing a single comment's thread
view the rest of the comments

[–] Nithanim@programming.dev 2 points 7 months ago (2 children)

Nice, thank you!

Though, the "quick" save-post-button seems broken. The "save" button in the context menu works normally, but the "quick" one has no toast message and does not update the post state.

[–] idunnololz@lemmy.world 3 points 7 months ago (1 children)

I found the cause. It's interesting. The v1.33.0 update brought way more responsive actions by adding a lot of code to handle them everywhere. When an action is fired, many screens will now listen to the action and do something in response. Commonly they will show a snackbar and maybe also update the state. However actions are ephemeral so actions will be marked "handled" whenever they are dealt with. The post screen is a screen that is placed on top of the community screen, however the layout is a very flexible one, eg. on tablets both screens are shown at the same time. So even on a small screen both screens are "active". Since the community screen also shows a list of posts, it's also listening to post actions. However they both consume these actions. Since the community screen came first, it gets the "post saved" action first and will mark it as handled. Thus the post screen will never get the event which is why this broke.

As a fix I'm going to change the logic so that all action "listeners" are always called. This is preferable in the case where a post is saved because the post should update on both the community screen and the post screen.

[–] Nithanim@programming.dev 2 points 7 months ago

Thank you for your detailed answer! Seems like you got a cool but complex system in place. I am so glad I mainly fumble around in backend. Frontend becomes so absurdly tangled so fast 😂

[–] idunnololz@lemmy.world 2 points 7 months ago

Dammit I think I broke it again. Looking into it now. It does work, it just does update state.