[feat/#18] 메인화면 api 연동 #21
Conversation
|
Warning Rate limit exceeded@vvan2 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 23 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (1)
WalkthroughAdds remote API integration for home posts: new Retrofit service, DTOs, datasource, repository, DI bindings, ViewModel, and UI wiring; restructures network response model; updates build config and manifest to source BASE_URL from properties and enable cleartext traffic; adjusts home UI composables to render popular and promotion posts. Changes
Sequence Diagram(s)sequenceDiagram
participant UI as HomeScreen
participant VM as HomeViewModel
participant Repo as PostRepositoryImpl
participant DS as PostDataSourceImpl
participant Service as PostService
participant API as Remote API
UI->>VM: collect state
VM->>VM: init -> fetchPopularPosts(), fetchPromotionPosts()
VM->>Repo: getPopularPost()
Repo->>DS: getPopularPost()
DS->>Service: retrofit.getPopularPost()
Service->>API: GET /posts/popular
API-->>Service: BaseResponse<PostResponseDto>
Service-->>DS: BaseResponse<PostResponseDto>
DS-->>Repo: BaseResponse<PostResponseDto>
rect rgb(220,240,220)
Note over Repo: evaluate isSuccess / map result
alt success
Repo-->>VM: Result.success(List<PostPopularEntity>)
else failure
Repo-->>VM: Result.failure(Exception)
end
end
VM->>VM: update HomeContract state
VM-->>UI: emit state
UI->>UI: render LazyRow(s)
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 8
🧹 Nitpick comments (6)
app/src/main/java/com/hsLink/hslink/presentation/home/state/HomeContract.kt (1)
7-15: Remove unnecessary empty body.The data class doesn't need an empty body block. Data classes with only constructor parameters can omit the body entirely.
Apply this diff:
@Immutable data class HomeContract ( val isLoading: Boolean = false, val error: String? = null, val postPopular : List<PostPopularEntity> = emptyList(), val postPromotion : List<PostPromotionEntity> = emptyList() -){ - -} +)app/src/main/java/com/hsLink/hslink/domain/model/PostResponseEntity.kt (1)
3-3: Remove unused serialization import.Domain entities shouldn't reference serialization libraries—serialization belongs in the data layer (DTOs). This import is unused and should be removed.
Apply this diff:
package com.hsLink.hslink.domain.model -import kotlinx.serialization.SerialName - data class PostPopularEntity (app/src/main/java/com/hsLink/hslink/presentation/home/component/HomeCardItem.kt (1)
40-47: Consider extracting HomePromotionPost to a dedicated models package.While co-locating the data class here works, presentation models are typically better organized in a separate package (e.g.,
presentation.home.model) for improved discoverability and maintainability.app/src/main/java/com/hsLink/hslink/data/remote/datasourceimpl/PostDataSourceImpl.kt (1)
10-20: Consider removing the redundant data source layer.
PostDataSourceImplis a simple pass-through wrapper that adds no value—it delegates directly toPostServicewithout transformation, error handling, or additional logic. This introduces unnecessary complexity and indirection.Consider having
PostRepositoryImplinject and usePostServicedirectly, eliminating the data source interface and implementation. The data source layer becomes valuable when you need to aggregate multiple services, add caching, or apply cross-cutting concerns—none of which are present here.app/src/main/java/com/hsLink/hslink/presentation/home/viewmodel/HomeViewModel.kt (1)
27-47: SetisLoadingbefore launching the fetch.Right now we only ever write
isLoading = false, so subsequent refreshes never emit a “loading” state to the UI. Please pushisLoading = true(and clear any stale error) before calling the repository in both fetchers so consumers can display progress.Apply this diff pattern in each fetch:
fun fetchPopularPosts() { viewModelScope.launch { + _state.update { it.copy(isLoading = true, error = null) } postRepository.getPopularPost() .onSuccess { posts -> _state.update { state ->app/src/main/java/com/hsLink/hslink/data/repositoryimpl/PostRepositoryImpl.kt (1)
10-31: Depend on thePostDataSourcecontract, not its concrete impl.Injecting
PostDataSourceImplcouples the repository to one implementation and makes testing/mocking harder. Please inject thePostDataSourceinterface instead and adjust the calls accordingly.Example adjustment:
-import com.hsLink.hslink.data.remote.datasourceimpl.PostDataSourceImpl +import com.hsLink.hslink.data.remote.datasource.PostDataSource -class PostRepositoryImpl @Inject constructor( - private val postDataSourceImpl: PostDataSourceImpl, +class PostRepositoryImpl @Inject constructor( + private val postDataSource: PostDataSource, ) : PostRepository { override suspend fun getPopularPost(): Result<List<PostPopularEntity>> = runCatching { - val response = postDataSourceImpl.getPopularPost() + val response = postDataSource.getPopularPost()
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (21)
app/build.gradle.kts(3 hunks)app/src/main/AndroidManifest.xml(1 hunks)app/src/main/java/com/hsLink/hslink/core/network/BaseResponse.kt(1 hunks)app/src/main/java/com/hsLink/hslink/data/di/DataSourceModule.kt(1 hunks)app/src/main/java/com/hsLink/hslink/data/di/NetworkModule.kt(3 hunks)app/src/main/java/com/hsLink/hslink/data/di/RepositoryModule.kt(2 hunks)app/src/main/java/com/hsLink/hslink/data/dto/request/PostRequestDto.kt(1 hunks)app/src/main/java/com/hsLink/hslink/data/dto/response/PostResponseDto.kt(1 hunks)app/src/main/java/com/hsLink/hslink/data/remote/datasource/PostDataSource.kt(1 hunks)app/src/main/java/com/hsLink/hslink/data/remote/datasourceimpl/PostDataSourceImpl.kt(1 hunks)app/src/main/java/com/hsLink/hslink/data/repositoryimpl/PostRepositoryImpl.kt(1 hunks)app/src/main/java/com/hsLink/hslink/data/service/home/PostService.kt(1 hunks)app/src/main/java/com/hsLink/hslink/domain/model/PostResponseEntity.kt(1 hunks)app/src/main/java/com/hsLink/hslink/domain/repository/PostRepository.kt(1 hunks)app/src/main/java/com/hsLink/hslink/presentation/home/component/HomeCardItem.kt(3 hunks)app/src/main/java/com/hsLink/hslink/presentation/home/component/HomePostContainer.kt(2 hunks)app/src/main/java/com/hsLink/hslink/presentation/home/navigation/HomeNavigation.kt(1 hunks)app/src/main/java/com/hsLink/hslink/presentation/home/screen/HomeScreen.kt(5 hunks)app/src/main/java/com/hsLink/hslink/presentation/home/state/HomeContract.kt(1 hunks)app/src/main/java/com/hsLink/hslink/presentation/home/viewmodel/HomeViewModel.kt(1 hunks)app/src/main/java/com/hsLink/hslink/presentation/main/MainNavigator.kt(2 hunks)
🧰 Additional context used
🧬 Code graph analysis (1)
app/src/main/java/com/hsLink/hslink/presentation/home/screen/HomeScreen.kt (1)
app/src/main/java/com/hsLink/hslink/presentation/home/component/HomeCardItem.kt (1)
HomeCardItem(48-117)
🪛 detekt (1.23.8)
app/src/main/java/com/hsLink/hslink/presentation/home/state/HomeContract.kt
[warning] 13-15: The class or object HomeContract is empty.
(detekt.empty-blocks.EmptyClassBlock)
app/src/main/java/com/hsLink/hslink/data/dto/request/PostRequestDto.kt
[warning] 3-4: The class or object PostRequestDto is empty.
(detekt.empty-blocks.EmptyClassBlock)
🔇 Additional comments (13)
app/src/main/java/com/hsLink/hslink/presentation/main/MainNavigator.kt (1)
72-74: LGTM! Consistent navigation pattern.The implementation correctly follows the existing pattern for navigation methods in this class and allows flexible navigation to Home with custom
NavOptions.app/src/main/java/com/hsLink/hslink/presentation/home/navigation/HomeNavigation.kt (1)
9-9: LGTM! Clean package reorganization.The import path update aligns with the new screen subpackage structure without affecting functionality.
app/src/main/java/com/hsLink/hslink/presentation/home/component/HomeCardItem.kt (1)
49-56: Verify intended usage of routeId parameter.The
routeIdparameter is accepted but not used within the composable. If it's intended for navigation on click, the click handler is missing. If it's for future use, consider documenting that intent.app/src/main/java/com/hsLink/hslink/core/network/BaseResponse.kt (1)
7-16: LGTM! Cleaner response structure.The flattened BaseResponse structure is simpler and more maintainable than the previous nested design. The PR context confirms that dependent services (PostService, data sources) have been updated to use this new contract.
app/src/main/java/com/hsLink/hslink/data/dto/response/PostResponseDto.kt (2)
8-43: LGTM! Well-structured DTOs with proper serialization.The DTO structure cleanly separates data transfer concerns from domain models. All serialization annotations are correctly applied.
Minor formatting note: Line 43 has extra blank lines after the closing parenthesis—purely cosmetic.
46-62: LGTM! Clean DTO-to-entity mappings.The extension functions provide a clear boundary between the data layer and domain layer, with straightforward field mappings.
app/src/main/java/com/hsLink/hslink/data/di/NetworkModule.kt (2)
51-60: LGTM! Standard Retrofit setup.The conversion from expression body to block body is a neutral stylistic change with no functional impact.
62-65: LGTM! Proper DI wiring for PostService.The provider function correctly creates the PostService instance using Retrofit's standard pattern.
app/src/main/java/com/hsLink/hslink/data/remote/datasource/PostDataSource.kt (1)
7-11: LGTM!Clean interface definition with appropriate suspend functions for async data fetching.
app/src/main/java/com/hsLink/hslink/data/service/home/PostService.kt (1)
9-15: LGTM!Standard Retrofit service interface with properly defined endpoints.
app/src/main/java/com/hsLink/hslink/data/di/RepositoryModule.kt (1)
21-25: LGTM!Proper Dagger-Hilt binding for the new repository.
app/src/main/java/com/hsLink/hslink/presentation/home/component/HomePostContainer.kt (1)
39-43: LGTM!Good addition of
@Immutableannotation for Compose performance optimization, and the simplified data class structure aligns with separation of concerns.app/src/main/java/com/hsLink/hslink/domain/repository/PostRepository.kt (1)
6-9: LGTM!Clean domain repository contract using Kotlin's
Resulttype for proper error handling.
| val properties = Properties().apply { | ||
| val localPropertiesFile = project.rootProject.file("local.properties") | ||
| if (localPropertiesFile.exists()) { | ||
| load(localPropertiesFile.inputStream()) | ||
| } | ||
| load(project.rootProject.file("local.properties").inputStream()) | ||
| } |
There was a problem hiding this comment.
Add error handling for missing local.properties file.
The unconditional load of local.properties will cause build failure if the file doesn't exist. This is particularly problematic for new developers setting up the project or in CI/CD environments.
Apply this diff to add defensive checks:
val properties = Properties().apply {
- load(project.rootProject.file("local.properties").inputStream())
+ val localPropertiesFile = project.rootProject.file("local.properties")
+ if (localPropertiesFile.exists()) {
+ load(localPropertiesFile.inputStream())
+ } else {
+ throw GradleException("local.properties file not found. Please create it with base.url property.")
+ }
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| val properties = Properties().apply { | |
| val localPropertiesFile = project.rootProject.file("local.properties") | |
| if (localPropertiesFile.exists()) { | |
| load(localPropertiesFile.inputStream()) | |
| } | |
| load(project.rootProject.file("local.properties").inputStream()) | |
| } | |
| val properties = Properties().apply { | |
| val localPropertiesFile = project.rootProject.file("local.properties") | |
| if (localPropertiesFile.exists()) { | |
| load(localPropertiesFile.inputStream()) | |
| } else { | |
| throw GradleException("local.properties file not found. Please create it with base.url property.") | |
| } | |
| } |
🤖 Prompt for AI Agents
In app/build.gradle.kts around lines 14 to 16, the code unconditionally loads
local.properties which will throw if the file is missing; add a defensive check
to see if project.rootProject.file("local.properties") exists and isFile before
calling load, and if it doesn't exist either skip loading (optionally log a
warning) or fall back to default properties so the build can proceed; ensure you
still load when present and handle IOExceptions by catching and logging them
rather than letting them fail the build.
| ) | ||
| //buildConfigField("String", "BASE_URL", properties["base.url"].toString()) | ||
|
|
||
| buildConfigField("String", "BASE_URL", "\"${properties["base.url"]}\"") |
There was a problem hiding this comment.
Add null safety for base.url property access.
Direct property access via properties["base.url"] can fail with a NullPointerException if the property is missing. This would result in cryptic build errors.
Apply this diff to add null safety with a clear error message:
- buildConfigField("String", "BASE_URL", "\"${properties["base.url"]}\"")
+ buildConfigField("String", "BASE_URL", "\"${properties["base.url"] ?: error("base.url property is missing in local.properties")}\"")📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| buildConfigField("String", "BASE_URL", "\"${properties["base.url"]}\"") | |
| buildConfigField("String", "BASE_URL", "\"${properties["base.url"] ?: error("base.url property is missing in local.properties")}\"") |
🤖 Prompt for AI Agents
In app/build.gradle.kts around line 31, the direct access properties["base.url"]
can be null and cause an NPE; change it to safely unwrap the property and fail
fast with a clear message (e.g. use requireNotNull(properties["base.url"]) {
"Missing required project property 'base.url'" } or check
properties.containsKey("base.url") and throw a GradleException) and then use the
resulting non-null value when calling buildConfigField (preserving the
surrounding quoted string expected by buildConfigField).
| getDefaultProguardFile("proguard-android-optimize.txt"), | ||
| "proguard-rules.pro" | ||
| ) | ||
| buildConfigField("String", "BASE_URL", "\"${properties["base.url"]}\"") |
There was a problem hiding this comment.
Add null safety for base.url property access in release build.
Same issue as in defaultConfig - the property access lacks null safety.
Apply this diff:
- buildConfigField("String", "BASE_URL", "\"${properties["base.url"]}\"")
+ buildConfigField("String", "BASE_URL", "\"${properties["base.url"] ?: error("base.url property is missing in local.properties")}\"")📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| buildConfigField("String", "BASE_URL", "\"${properties["base.url"]}\"") | |
| buildConfigField("String", "BASE_URL", "\"${properties["base.url"] ?: error("base.url property is missing in local.properties")}\"") |
🤖 Prompt for AI Agents
In app/build.gradle.kts around line 42, the buildConfigField call uses
properties["base.url"] without null-safety; change it to use a safe cast and
fallback or fail fast — e.g., replace the direct access with
(properties["base.url"] as? String) ?: error("base.url property is required") so
the value is null-safe and provides a clear error if missing.
| <application | ||
| android:name=".HsuConnectApplication" | ||
| android:allowBackup="true" | ||
| android:usesCleartextTraffic="true" |
There was a problem hiding this comment.
Security concern: Restrict cleartext traffic to development only.
Enabling usesCleartextTraffic="true" globally allows unencrypted HTTP traffic, which exposes user data to interception and man-in-the-middle attacks. This should not be shipped to production.
Recommended solution: Use a Network Security Configuration file to allow cleartext traffic only for specific development domains:
- Create
res/xml/network_security_config.xml:
<?xml version="1.0" encoding="utf-8"?>
<network-security-config>
<domain-config cleartextTrafficPermitted="true">
<domain includeSubdomains="true">localhost</domain>
<domain includeSubdomains="true">10.0.2.2</domain>
<!-- Add your dev server domains here -->
</domain-config>
</network-security-config>- Reference it in the manifest:
- android:usesCleartextTraffic="true"
+ android:networkSecurityConfig="@xml/network_security_config"Alternatively, use build-variant-specific manifests to enable this only in debug builds.
| @Binds | ||
| abstract fun bindePostRemoteDataSource( | ||
| postDataSourceImpl: PostDataSourceImpl, | ||
| ): PostDataSource | ||
| } No newline at end of file |
There was a problem hiding this comment.
Fix typo in method name.
The method name bindePostRemoteDataSource has a typo—it should be bindPostRemoteDataSource for consistency with Dagger naming conventions.
Apply this diff:
@Binds
- abstract fun bindePostRemoteDataSource(
+ abstract fun bindPostRemoteDataSource(
postDataSourceImpl: PostDataSourceImpl,
): PostDataSource📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| @Binds | |
| abstract fun bindePostRemoteDataSource( | |
| postDataSourceImpl: PostDataSourceImpl, | |
| ): PostDataSource | |
| } | |
| @Binds | |
| abstract fun bindPostRemoteDataSource( | |
| postDataSourceImpl: PostDataSourceImpl, | |
| ): PostDataSource | |
| } |
🤖 Prompt for AI Agents
In app/src/main/java/com/hsLink/hslink/data/di/DataSourceModule.kt around lines
13 to 17, the Binds method name `bindePostRemoteDataSource` has a typo; rename
it to `bindPostRemoteDataSource` so it follows naming conventions and matches
other DI bindings, updating the method declaration only (keep parameter type and
return type unchanged).
| import okhttp3.logging.HttpLoggingInterceptor | ||
| import retrofit2.Converter | ||
| import retrofit2.Retrofit | ||
| import timber.log.Timber |
There was a problem hiding this comment.
🧩 Analysis chain
Verify usage of Timber import.
The Timber import is added but not visibly used in the provided code. If it's unused, consider removing it.
🏁 Script executed:
#!/bin/bash
# Description: Check if Timber is used in NetworkModule.kt
# Search for Timber usage in the file
rg -n "Timber\." app/src/main/java/com/hsLink/hslink/data/di/NetworkModule.ktLength of output: 0
---
🏁 Script executed:
```shell
#!/bin/bash
# Check if file exists and view its content
if [ -f "app/src/main/java/com/hsLink/hslink/data/di/NetworkModule.kt" ]; then
echo "=== File exists. Content: ==="
cat "app/src/main/java/com/hsLink/hslink/data/di/NetworkModule.kt"
else
echo "File not found at specified path"
fi
echo ""
echo "=== Searching for any Timber reference (including imports) ==="
rg -n "Timber" app/src/main/java/com/hsLink/hslink/data/di/NetworkModule.kt
Length of output: 2038
Remove unused Timber import.
The Timber import at line 16 is not used anywhere in the file. Remove it.
🤖 Prompt for AI Agents
In app/src/main/java/com/hsLink/hslink/data/di/NetworkModule.kt around line 16,
the import "timber.log.Timber" is unused; remove that import line to clean up
unused dependencies and avoid lint/compile warnings, leaving the rest of the
file unchanged.
| class PostRequestDto { | ||
| } No newline at end of file |
There was a problem hiding this comment.
🧩 Analysis chain
Empty class serves no purpose.
This class has no fields or methods. If it's a placeholder for future request bodies, consider removing it until actually needed (YAGNI principle). Alternatively, if requirements are known, add the necessary fields now.
Run the following script to verify if this class is referenced anywhere in the codebase:
If no usages are found, consider removing this file to keep the codebase clean.
🏁 Script executed:
#!/bin/bash
# Description: Check if PostRequestDto is used anywhere in the codebase
# Search for imports of PostRequestDto
rg -n "import.*PostRequestDto" -g "*.kt"
# Search for usages of PostRequestDto (excluding the definition itself)
rg -n "PostRequestDto" -g "*.kt" -C 2 | grep -v "class PostRequestDto"Length of output: 264
Remove unused empty class PostRequestDto.
Verification confirms this class is not imported or used anywhere in the codebase. It serves no purpose and should be deleted to maintain code cleanliness and avoid future confusion.
🧰 Tools
🪛 detekt (1.23.8)
[warning] 3-4: The class or object PostRequestDto is empty.
(detekt.empty-blocks.EmptyClassBlock)
🤖 Prompt for AI Agents
In app/src/main/java/com/hsLink/hslink/data/dto/request/PostRequestDto.kt around
lines 3 to 4, remove the unused empty class PostRequestDto; delete the file
entirely (or remove the class declaration) and verify there are no imports or
references left in the project, then run a full build to ensure no compilation
errors.
| LazyRow( | ||
| modifier = Modifier.padding(start = 16.dp, end = 16.dp), | ||
| horizontalArrangement = Arrangement.spacedBy(12.dp) | ||
| ) { | ||
| items(promotionPosts) { post -> | ||
| HomeCardItem( | ||
| userName = post.title, | ||
| userMajor = post.summary, | ||
| userInfo = post.author, | ||
| userId = post.studentId, | ||
| routeId = post.id, | ||
| modifier = Modifier.width(250.dp) | ||
| ) | ||
| } |
There was a problem hiding this comment.
Wire onPromotionClick into the promotion cards.
HomeScreen exposes onPromotionClick, but the LazyRow never invokes it, so the new handler is a no-op and promotion cards stay non-interactive. Please add a Modifier.clickable { onPromotionClick(post) } (and the import) when building each card.
Suggested fix:
-import androidx.compose.foundation.layout.PaddingValues
+import androidx.compose.foundation.clickable
+import androidx.compose.foundation.layout.PaddingValues
@@
items(promotionPosts) { post ->
HomeCardItem(
userName = post.title,
userMajor = post.summary,
userInfo = post.author,
userId = post.studentId,
routeId = post.id,
- modifier = Modifier.width(250.dp)
+ modifier = Modifier
+ .width(250.dp)
+ .clickable { onPromotionClick(post) }
)
}
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| LazyRow( | |
| modifier = Modifier.padding(start = 16.dp, end = 16.dp), | |
| horizontalArrangement = Arrangement.spacedBy(12.dp) | |
| ) { | |
| items(promotionPosts) { post -> | |
| HomeCardItem( | |
| userName = post.title, | |
| userMajor = post.summary, | |
| userInfo = post.author, | |
| userId = post.studentId, | |
| routeId = post.id, | |
| modifier = Modifier.width(250.dp) | |
| ) | |
| } | |
| LazyRow( | |
| modifier = Modifier.padding(start = 16.dp, end = 16.dp), | |
| horizontalArrangement = Arrangement.spacedBy(12.dp) | |
| ) { | |
| items(promotionPosts) { post -> | |
| HomeCardItem( | |
| userName = post.title, | |
| userMajor = post.summary, | |
| userInfo = post.author, | |
| userId = post.studentId, | |
| routeId = post.id, | |
| modifier = Modifier | |
| .width(250.dp) | |
| .clickable { onPromotionClick(post) } | |
| ) | |
| } | |
| } |
🤖 Prompt for AI Agents
In app/src/main/java/com/hsLink/hslink/presentation/home/screen/HomeScreen.kt
around lines 184 to 197, the LazyRow builds promotion HomeCardItem instances but
does not wire the exposed onPromotionClick handler, leaving cards
non-interactive; update the HomeCardItem call to add a clickable modifier that
calls onPromotionClick(post) (e.g., combine Modifier.width(250.dp).clickable {
onPromotionClick(post) }) and add the necessary import for
androidx.compose.foundation.clickable so each promotion card invokes the handler
when tapped.
ISSUE
❗ WORK DESCRIPTION
📸 SCREENSHOT
📢 TO REVIEWERS
Summary by CodeRabbit
New Features
Chores