Mastodon
/
pachli-android
mirror of https://github.com/pachli/pachli-android.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
pachli-android/core/data/build.gradle.kts

56 lines
1.7 KiB
Plaintext
Raw Normal View History

refactor: Modularise "about" activities (#405) Continue modularisation by moving activities in the "About" feature to a new `feature.about` module. Implement `feature.about: - Move `AboutActivity`, `LicenseActivity`, and `PrivacyPolicyActivity` here. - Update `markdown2resource` plugin to work with libraries Implement `core.data`: - Types and repositories used through the app - Move `InstanceInfo` and `InstanceInfoRepository` here so they are available to `feature.about`. Implement `core.ui`: - App-specific views, spans, and other UI content - Move `ClickableSpanTextView` and `NoUnderlineURLSpan` here so they are available to `feature.about`.
2024-02-02 15:14:31 +01:00
/*
* Copyright 2024 Pachli Association
refactor compose & announcements to coroutines (#2446) * refactor compose & announcements to coroutines * fix code formatting * add javadoc to InstanceInfoRepository * fix comments in ImageDownsizer * remove unused Either extensions * add explicit return type for InstanceInfoRepository.getEmojis * make ComposeViewModel.pickMedia return Result * cleanup code in ImageDownsizer
2022-04-21 18:46:21 +02:00
*
refactor: Transition from Tusky to Pachli - Rename packages to app.pachli.* - Switch to Pachli icons (blue / orange) - Reset database schema version to 1 - Reset versionCode to 1 and versionName to "1.0" - Update colour scheme, use colorPrimary etc through the app - Use Material UI components for toolbars - Use "Pachli" in strings (UI, constants, etc) - Update copyright on code I contributed - Update README - Update fastlane metadata
2023-09-05 13:28:56 +02:00
* This file is a part of Pachli.
refactor compose & announcements to coroutines (#2446) * refactor compose & announcements to coroutines * fix code formatting * add javadoc to InstanceInfoRepository * fix comments in ImageDownsizer * remove unused Either extensions * add explicit return type for InstanceInfoRepository.getEmojis * make ComposeViewModel.pickMedia return Result * cleanup code in ImageDownsizer
2022-04-21 18:46:21 +02:00
*
* This program is free software; you can redistribute it and/or modify it under the terms of the
* GNU General Public License as published by the Free Software Foundation; either version 3 of the
* License, or (at your option) any later version.
*
refactor: Transition from Tusky to Pachli - Rename packages to app.pachli.* - Switch to Pachli icons (blue / orange) - Reset database schema version to 1 - Reset versionCode to 1 and versionName to "1.0" - Update colour scheme, use colorPrimary etc through the app - Use Material UI components for toolbars - Use "Pachli" in strings (UI, constants, etc) - Update copyright on code I contributed - Update README - Update fastlane metadata
2023-09-05 13:28:56 +02:00
* Pachli is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even
refactor compose & announcements to coroutines (#2446) * refactor compose & announcements to coroutines * fix code formatting * add javadoc to InstanceInfoRepository * fix comments in ImageDownsizer * remove unused Either extensions * add explicit return type for InstanceInfoRepository.getEmojis * make ComposeViewModel.pickMedia return Result * cleanup code in ImageDownsizer
2022-04-21 18:46:21 +02:00
* the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General
* Public License for more details.
*
chore: Update copyright notice to refer to Pachli for the license (#201) Previous copyright notice mentioned that the license should have been distributed with Tusky. Correct that to Pachli. This does not change the copyright assignment, only the instructions as to where to find the license.
2023-10-26 16:41:12 +02:00
* You should have received a copy of the GNU General Public License along with Pachli; if not,
* see <http://www.gnu.org/licenses>.
*/
refactor compose & announcements to coroutines (#2446) * refactor compose & announcements to coroutines * fix code formatting * add javadoc to InstanceInfoRepository * fix comments in ImageDownsizer * remove unused Either extensions * add explicit return type for InstanceInfoRepository.getEmojis * make ComposeViewModel.pickMedia return Result * cleanup code in ImageDownsizer
2022-04-21 18:46:21 +02:00
refactor: Modularise "about" activities (#405) Continue modularisation by moving activities in the "About" feature to a new `feature.about` module. Implement `feature.about: - Move `AboutActivity`, `LicenseActivity`, and `PrivacyPolicyActivity` here. - Update `markdown2resource` plugin to work with libraries Implement `core.data`: - Types and repositories used through the app - Move `InstanceInfo` and `InstanceInfoRepository` here so they are available to `feature.about`. Implement `core.ui`: - App-specific views, spans, and other UI content - Move `ClickableSpanTextView` and `NoUnderlineURLSpan` here so they are available to `feature.about`.
2024-02-02 15:14:31 +01:00
plugins {
alias(libs.plugins.pachli.android.library)
alias(libs.plugins.pachli.android.hilt)
change: Implement more of FiltersRepository (#816) The previous code had a number of problems, including: - Calls to the filters API were scattered through UI and viewmodel code. - Repeated places where the differences between the v1 and v2 Mastodon filters API had to be handled. - UI and viewmodel code using the network filter classes, which tied them to the API implementation. - Error handling was inconsistent. Fix this. ## FiltersRepository - All filter management now goes through `FiltersRepository`. - `FiltersRepository` exposes the current set of filters as a `StateFlow`, and automatically updates it when the current server changes or any changes to filters are made. This makes `FilterChangeEvent` obsolete. - Other operations on filters are exposed through `FiltersRepository` as functions for viewmodels to call. - Within the bulk of the app a new `Filter` class is used to represent a filter; handling the differences between the v1 and v2 APIs is encapsulated in `FiltersRepository`. - Represent errors when handling filters as subclasses of `PachliError`, and use `Result<V, E>` throughout, including using `ApiResult` for all filter API results. - Provide different types to distinguish between new-and-unsaved filters, new-and-unsaved keywords, and in-progress edits to filters. ## Editing filters - Accept an optional complete filter, or filter ID, as parameters in the intent that launches `EditFilterActivity`. Pass those to the viewmodel using assisted injection so the viewmodel has the info immediately. - In the viewmodel use a new `FilterViewData` type to model the data used to display and edit the filter. - Start using the UiSuccess/UiError model. Refrain from cutting over to full the action implementation as that would be a much larger change. - Use `FiltersRepository` instead of making any API calls directly. ## Listing filters - Use `FiltersRepository` instead of making any API calls directly. ## EventHub - Remove `FilterChangedEvent`. Update everywhere that used it to use the flow from `FiltersRepository`.
2024-07-14 15:36:52 +02:00
alias(libs.plugins.kotlin.parcelize)
refactor: Modularise "about" activities (#405) Continue modularisation by moving activities in the "About" feature to a new `feature.about` module. Implement `feature.about: - Move `AboutActivity`, `LicenseActivity`, and `PrivacyPolicyActivity` here. - Update `markdown2resource` plugin to work with libraries Implement `core.data`: - Types and repositories used through the app - Move `InstanceInfo` and `InstanceInfoRepository` here so they are available to `feature.about`. Implement `core.ui`: - App-specific views, spans, and other UI content - Move `ClickableSpanTextView` and `NoUnderlineURLSpan` here so they are available to `feature.about`.
2024-02-02 15:14:31 +01:00
}
refactor compose & announcements to coroutines (#2446) * refactor compose & announcements to coroutines * fix code formatting * add javadoc to InstanceInfoRepository * fix comments in ImageDownsizer * remove unused Either extensions * add explicit return type for InstanceInfoRepository.getEmojis * make ComposeViewModel.pickMedia return Result * cleanup code in ImageDownsizer
2022-04-21 18:46:21 +02:00
refactor: Modularise "about" activities (#405) Continue modularisation by moving activities in the "About" feature to a new `feature.about` module. Implement `feature.about: - Move `AboutActivity`, `LicenseActivity`, and `PrivacyPolicyActivity` here. - Update `markdown2resource` plugin to work with libraries Implement `core.data`: - Types and repositories used through the app - Move `InstanceInfo` and `InstanceInfoRepository` here so they are available to `feature.about`. Implement `core.ui`: - App-specific views, spans, and other UI content - Move `ClickableSpanTextView` and `NoUnderlineURLSpan` here so they are available to `feature.about`.
2024-02-02 15:14:31 +01:00
android {
namespace = "app.pachli.core.data"
defaultConfig {
testInstrumentationRunner = "androidx.test.runner.AndroidJUnitRunner"
}
}
dependencies {
refactor: Ongoing work to remove the `activeAccount` idiom (#964) Continue the work to remove the "activeAccount" idiom. - Uses a new PachliAccount type through most of the app. This holds information that was previously accessed separately (e.g., content filters, lists) in one place. The information is loaded when the app launches or the active account switches. - Fetching data when the account is switched / loaded simplifies error handling, as more code can now assume the data has already been loaded. If it hasn't the code path is simply unreachable. - This opens up the possibility of "acting as one account while logged in as another". E.g., have two accounts, and be logged in to one account and boost a post you've seen from your other account. - Add a database migration to populate existing accounts with default data when the user updates the app. - Refactor code that used those list and filter repositories to get the data from the PachliAccount instead. New local and remote data sources are implemented, and the list and filter repositories mediate between those sources. - Start a ViewModel for MainActivity, which includes: - Sending user actions as UiAction objects - Providing a flow of uiState for MainActivity to react to - Remove most uses of SharedPreferencesRepository from MainActivity - Show messages about errors that occur when logging in - Refactor intent routing in MainActivity to make the logic clearer. - Add new `core.data` types to push more `core.network` types out of the UI code - `core.data.model.MastodonList` for `core.network.model.MastoList` - `core.data.model.Server` for `core.network.model.Server` - Continue the work to send the Pachli account ID to the code that uses it. - Most view models now get the account ID via assisted injection. - QueuedMedia now includes the AccountEntity so it can operate with any account. Modify the `uploadMedia` API call to include explicit authentication details. --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2024-11-13 11:45:16 +01:00
// TODO: AccountManager currently exposes AccountEntity which must be re-exported.
api(projects.core.database)
fix: Update InstanceV1/V2 related types based on real-world usage (#476) Many servers that claim to be Mastodon-API compatible are not, as evidenced by the content they include in the responses to `/api/v1/instance` and `/api/v2/instance` requests. Work around the worst of the breakage by providing defaults or marking some fields as nullable (with a default null). Bugs have been reported against the relevant projects.
2024-02-28 00:02:03 +01:00
implementation(projects.core.common)
refactor: Remove `TabData` type (#576) `TabData` recorded the type of the timeline the user had added to a tab. `TimelineKind` is another type that records general information about configured timelines, with identical properties. There's no need for both, so remove `TabData` and use `TimelineKind` in its place. `TimelineKind` is itself mis-named; it's not just the timeline's kind but also holds data necessary to display that timeline (e.g., the list ID if it's a `.UserList`, or the hashtags if it's a `.Hashtags`) so rename to `Timeline` to better reflect its usage. Move it to a new `core.model` module.
2024-03-30 23:27:25 +01:00
implementation(projects.core.model)
refactor: Modularise "about" activities (#405) Continue modularisation by moving activities in the "About" feature to a new `feature.about` module. Implement `feature.about: - Move `AboutActivity`, `LicenseActivity`, and `PrivacyPolicyActivity` here. - Update `markdown2resource` plugin to work with libraries Implement `core.data`: - Types and repositories used through the app - Move `InstanceInfo` and `InstanceInfoRepository` here so they are available to `feature.about`. Implement `core.ui`: - App-specific views, spans, and other UI content - Move `ClickableSpanTextView` and `NoUnderlineURLSpan` here so they are available to `feature.about`.
2024-02-02 15:14:31 +01:00
implementation(projects.core.network)
refactor: Move AccountPreferenceDataStore to core.data (#730)
2024-06-10 16:54:14 +02:00
implementation(projects.core.preferences)
// PreferenceDataStore
implementation(libs.bundles.androidx)
refactor: Modularise "about" activities (#405) Continue modularisation by moving activities in the "About" feature to a new `feature.about` module. Implement `feature.about: - Move `AboutActivity`, `LicenseActivity`, and `PrivacyPolicyActivity` here. - Update `markdown2resource` plugin to work with libraries Implement `core.data`: - Types and repositories used through the app - Move `InstanceInfo` and `InstanceInfoRepository` here so they are available to `feature.about`. Implement `core.ui`: - App-specific views, spans, and other UI content - Move `ClickableSpanTextView` and `NoUnderlineURLSpan` here so they are available to `feature.about`.
2024-02-02 15:14:31 +01:00
refactor: Move StatusDisplayOptions and Repository to core.data (#731)
2024-06-10 17:29:09 +02:00
// ServerRepository
implementation(libs.semver)
fix: Prevent crash when Pachli is a share target (#659) Crash was occuring because the instance info hadn't been fetched, trying to take the last item of an empty list. To fix: - Expose the instance info as a state flow, with a default. New instance info is fetched whenever the active account changes. - Do the same for the emojis supported by the server. - Update call sites as appropriate. - Mark `InstanceInfoRepository` as `@Singleton` so it isn't repeatedly created causing fresh content fetches. The tests needed updating to get this to work. - Extract the network fake modules in to a network-test module so multiple other modules can use them. - Rewrite `InstanceInfoRepositoryTest` to use Hilt and use Turbine to test the new flows. Checking this showed cosmetic bugs in the About layout when instance info is missing, clean those up.
2024-04-28 18:19:13 +02:00
testImplementation(projects.core.networkTest)
refactor: Modularise "about" activities (#405) Continue modularisation by moving activities in the "About" feature to a new `feature.about` module. Implement `feature.about: - Move `AboutActivity`, `LicenseActivity`, and `PrivacyPolicyActivity` here. - Update `markdown2resource` plugin to work with libraries Implement `core.data`: - Types and repositories used through the app - Move `InstanceInfo` and `InstanceInfoRepository` here so they are available to `feature.about`. Implement `core.ui`: - App-specific views, spans, and other UI content - Move `ClickableSpanTextView` and `NoUnderlineURLSpan` here so they are available to `feature.about`.
2024-02-02 15:14:31 +01:00
testImplementation(libs.bundles.mockito)
refactor: Ongoing work to remove the `activeAccount` idiom (#964) Continue the work to remove the "activeAccount" idiom. - Uses a new PachliAccount type through most of the app. This holds information that was previously accessed separately (e.g., content filters, lists) in one place. The information is loaded when the app launches or the active account switches. - Fetching data when the account is switched / loaded simplifies error handling, as more code can now assume the data has already been loaded. If it hasn't the code path is simply unreachable. - This opens up the possibility of "acting as one account while logged in as another". E.g., have two accounts, and be logged in to one account and boost a post you've seen from your other account. - Add a database migration to populate existing accounts with default data when the user updates the app. - Refactor code that used those list and filter repositories to get the data from the PachliAccount instead. New local and remote data sources are implemented, and the list and filter repositories mediate between those sources. - Start a ViewModel for MainActivity, which includes: - Sending user actions as UiAction objects - Providing a flow of uiState for MainActivity to react to - Remove most uses of SharedPreferencesRepository from MainActivity - Show messages about errors that occur when logging in - Refactor intent routing in MainActivity to make the logic clearer. - Add new `core.data` types to push more `core.network` types out of the UI code - `core.data.model.MastodonList` for `core.network.model.MastoList` - `core.data.model.Server` for `core.network.model.Server` - Continue the work to send the Pachli account ID to the code that uses it. - Most view models now get the account ID via assisted injection. - QueuedMedia now includes the AccountEntity so it can operate with any account. Modify the `uploadMedia` API call to include explicit authentication details. --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2024-11-13 11:45:16 +01:00
testImplementation(libs.moshi)
testImplementation(libs.moshi.adapters)
ksp(libs.moshi.codegen)
testImplementation(projects.core.networkTest)
refactor: Modularise "about" activities (#405) Continue modularisation by moving activities in the "About" feature to a new `feature.about` module. Implement `feature.about: - Move `AboutActivity`, `LicenseActivity`, and `PrivacyPolicyActivity` here. - Update `markdown2resource` plugin to work with libraries Implement `core.data`: - Types and repositories used through the app - Move `InstanceInfo` and `InstanceInfoRepository` here so they are available to `feature.about`. Implement `core.ui`: - App-specific views, spans, and other UI content - Move `ClickableSpanTextView` and `NoUnderlineURLSpan` here so they are available to `feature.about`.
2024-02-02 15:14:31 +01:00
}