In a previous commit, I've added a code snippet that made an update query for each fetched summary that is already in the internal database. However, it did not take in to account that the same community can be related to different accounts. This commit fixes this issue by adding an additional filter to the update db query.
Previously, the app did not update any changes to a community after subscribing to it. Now the internal db is updated each time the list of subscribers is refreshed.
This commit fixes the issue where the 'swiping between posts' and 'mark post as read' options are enable. Previously, it only marked the first post as read, and not the ones that were swiped to. Now, all posts are marked read in these scenarios.
Signed-off-by: Balazs Toldi <balazs@toldi.eu>
This commit fixes an issue where the display name of a user makes it
impossible to load saved things. The problem is that the display name
was used in the url to load the saved things instead of the username.
Closes#179
Signed-off-by: Balazs Toldi <balazs@toldi.eu>
This commit allows the user to input the communities with their "!" prefix. Similarly, it also allows the "@" prefix for users when trying to navigate to them with their corresponding "go to" options.
Also fixes issues with these options in the Community and User pages.
This commit fixes issues where the sort type/time isn't loaded properly and the app resets back to NEW on the frontpage and Hot on Community pages.
Heads up: You might need to change the sort type in your settings if you see any issues.
See: https://github.com/LemmyNet/lemmy/pull/3403
For now, I guess we can try parsing the flag if it's present, and fall
back on assuming the associated user is *not* an admin.
- Setup Glide with OkHttp in the custom application
- Add PostEnricher framework, that allows to add more data to fetched Posts. This was used to fetch the RedGIFs preview from their API.
This commit changes how resolving links work. It will not use the resolve object function now for local instance links, as they would fail almost every time.
It also opens toasts in the application context instead of the activity context. This might prevent some crashes
