This branch implements search functionality across all articles that the user is subscribed to. In order to get more accurate searches, I used a fuzzy string searching library called fuzzywuzzy (originally implemented in Python, but using a Java port). I didn't get a chance to implement filtering due to time constraints.

https://github.com/xdrop/fuzzywuzzy

Closes #16

Added url trimming to AddFeedActivity.kt

List of Changes:

• Added StringOpeerations.kt operations file
• Refactored AddFeedActivity.kt
• Added UrlTrimTest.kt Unit test

Describe the bug After you add a feed (and possibly in other instances as well), all of the articles from the added feed dissappear when you either "bookmark" or "mark as read" on any article in the feedGroup.

To Reproduce Steps to reproduce the behavior:

1. Start the app.
2. Add a new feed.
3. Refresh the article view or feed view.
4. All the articles from the newly added feed, and the feed itselt should dissappear.
5. Triggering an activity and then returning will cause the feed to reappear.

Expected behavior After adding a feed, there should be no behaviour causing the articles and feed to dissappear, even if it is only for the UI.

Screenshots/Video

https://user-images.githubusercontent.com/34548959/142093723-e381fc5b-9f35-4e86-8dfe-471d8a3051c6.mp4

This branch implements a bookmarks page where you can view articles that you have bookmarked. The way that it works currently is that when you toggle the flag icon to remove a bookmark, your changes won't be saved to the database unless you go back to the main menu and then back to the bookmarks page. Here's a picture of how each article would look, sorry for the pixelation.

Using a Room database (layer of abstraction for SQLite), this branch implements persistence to allow a user's feeds to be saved on app close and reloaded on app open. This means that the user saves bandwidth by not having to retrieve feeds every time the lifecycle renews. It also means that the user can still read old articles they have retrieved that have since been removed from the feeds they subscribe to. The system could even be extended to allow the user to read entire feeds that have been removed which the user has retrieved (in their last published state, of course). Here is a demonstration of the persistence in action:

https://user-images.githubusercontent.com/34548959/139519294-020ace1f-a4d6-45d8-82f3-06b552b21003.mp4

Describe the bug Deleting a feed causes the article list to be cleared until refreshes.

To Reproduce Steps to reproduce the behavior:

1. Add two or more feeds.
2. Go to the feed view.
3. Delete one of the feeds.
4. Go to article view.
5. See that there are no articles.
6. Articles will come back after a refresh.

Expected behavior After deleting a feed, only articles from that feed should disappear.

This branch adds dynamic open-source license information. It is accessible via Settings > Open-Source Licenses. The list is generated upon compile time by a grade plugin as a JSON file, which is then used to render the list in the application.

https://user-images.githubusercontent.com/34548959/143969911-3a10a991-6ea2-4cf5-a3cc-0bfbbba35c5c.mp4

This branch adds the ability to delete a feed by long pressing on it and clicking "Delete". This will remove it from the database and feedList, so it will no longer show up in the application and will need to be re-added if the user would like to see it again.

This branch adds a settings activity. The main settings here are the theme and cache timings, but the provided composables allow for easy expansion in the future. This also implements the theming and cache timings in all the other activities. The settings also provide lots of information settings such as the open-source libraries used, links to the source code, releases, etc. There are some things not filled in with TODOs left in their place but this is intentional. We do not yet have all the information required to complete these items.

Previously, we were accessing MainActivity.feedGroup and other companion object variables. This is bad practice for clean code so instead, we should have each activity communicate with the database layer to retrieve the feeds on startup and write changes on exit. I also updated the Design Document with a section reflecting these changes.

This reimplements all of the code that we previously had into Kotlin. This includes the data classes, PullFeedTask, and MainActivity. It also more closely follows the solid design principles and has fewer code-smells by extracting long sections of code into different methods to split up the code base and make it more readable, and less interdependent.

Describe the bug The aspect ratio of the images next to articles and feeds in ArticleCard and FeedCard do not have a constant aspect ratio on different size phone screens. On one phone, it may be square, while on others, it can be a taller rectangle.

To Reproduce Steps to reproduce the behaviour:

1. Get a phone with a taller aspect ratio that has a thinner aspect ratio than 2:1.
2. Open the application.

Expected behaviour The aspect ratio should be consistent across all devices

Screenshots Taller aspect ratio:

Wider aspect ratio:

Notice that neither of these two have "square" images as is intended. One is too tall, the other is two wise, running the same code base.