Skip to content

fix: 스크롤 기능 추가#115

Merged
Dongnyoung merged 1 commit into
devfrom
fix/#114
May 27, 2026
Merged

fix: 스크롤 기능 추가#115
Dongnyoung merged 1 commit into
devfrom
fix/#114

Conversation

@Dongnyoung

@Dongnyoung Dongnyoung commented May 27, 2026

Copy link
Copy Markdown
Contributor

🚀 Summary

  • 스크롤기능

✨ Description

  • 스크롤 기능을 추가하였습니다!

🎲 Issue Number

close #114

@vercel

vercel Bot commented May 27, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
dealit Ready Ready Preview, Comment May 27, 2026 3:46pm

@Dongnyoung
Dongnyoung merged commit e0d6ef8 into dev May 27, 2026
3 checks passed

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request integrates bottom navigation across various pages (such as mypage, search, chat, and notifications) by wrapping them in RouteTabShell. It also updates navigation handlers to use explicit paths instead of router.back(), and applies layout constraints (h-dvh, min-h-0, overflow-hidden) to prevent scrolling issues. The reviewer feedback recommends explicitly importing ProductListType from ../products/index to avoid resolution ambiguity, and safely handling external URLs in the onTargetUrl callback within NotificationsPage to prevent routing errors.

Comment thread src/app/auctions/page.tsx

import AuctionListScreen from "./index";
import type { UnifiedSearchResultType } from "@/services/product/search/types";
import type { ProductListType } from "../products";

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

../products와 같이 Next.js의 라우트 디렉토리를 직접 임포트하는 경우, 빌드 환경이나 테스트 도구(Jest 등)에 따라 파일 해소(resolution) 모호성이 발생할 수 있습니다. src/app/products 디렉토리에는 page.tsxindex.tsx가 공존하고 있으므로, 명확하게 ../products/index에서 타입을 임포트하거나 공통 타입을 별도의 타입 파일로 분리하는 것이 안전합니다.

Suggested change
import type { ProductListType } from "../products";
import type { ProductListType } from "../products/index";

onAuctionClick={(id) => router.push(`/auctions/${id}`)}
onWinningBidClick={() => router.push("/notifications")}
onOutbidClick={() => router.push("/notifications")}
onTargetUrl={(url) => router.push(url)}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

onTargetUrl 콜백에서 router.push(url)을 직접 호출하고 있습니다. 만약 알림의 targetUrl이 외부 링크(예: https://... 또는 http://...)인 경우, Next.js의 router.push는 이를 올바르게 처리하지 못하고 내부 경로로 오인하거나 에러를 발생시킬 수 있습니다.\n\n따라서 URL이 외부 링크인지 확인하는 로직을 추가하여, 외부 링크일 경우 window.location.href를 사용하도록 분기 처리하는 것이 안전합니다.

        onTargetUrl={(url) => {\n          if (url.startsWith("http://") || url.startsWith("https://")) {\n            window.location.href = url;\n          } else {\n            router.push(url);\n          }\n        }}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[fix] 스크롤 기능

1 participant