Conversation
홈은 뷰포트가 정해지기 전에 같은 크기의 스켈레톤을 그리고, 테두리·글자 스케일·관리자 배너 조회와 로컬 3000 포트를 맞춘다. Co-authored-by: Cursor <cursoragent@cursor.com>
fix: 첫 화면 정적 스켈레톤과 스타일·관리자 지표
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
develop가 data보다 뒤처져 다음 승격이 막혀 있어, 이미 data에 있는 머지 커밋만 포함한다.
…-20260924 sync: data 승격 머지를 develop에 포함한다
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 47e9342b76
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
접힌 패널이 지도를 가리지 않게 하고, 서비스 롤 설정 실패도 banner_read_failed로 막는다. Co-authored-by: Cursor <cursoragent@cursor.com>
fix: 스켈레톤 해제와 배너 실패 코드
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c71e812268
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| return () => { | ||
| delete document.documentElement.dataset.homeChromeReady; | ||
| }; |
There was a problem hiding this comment.
On mobile, home-client.tsx deliberately stops rendering HomeControlPanel while isMapFullscreen is true, so this cleanup removes data-home-chrome-ready even though the home map has already loaded. The persistent HomeStaticSkeleton then becomes visible again and overlays animated placeholder bars on the fullscreen map. Fresh evidence in the current tree is the new readiness cleanup combined with the fullscreen render condition; keep the loaded state independent of this conditionally mounted control panel, or remove the skeleton once real chrome has appeared.
Useful? React with 👍 / 👎.
| "dev": "node scripts/run-local-dev.mjs --port 3000", | ||
| "dev:local": "node scripts/run-local-dev.mjs --port 3000", |
There was a problem hiding this comment.
When a developer runs the newly configured default server and starts a local nightly run with APP_PORT=3000, validateLocalEnvironment in scripts/run-nightly-regression.mjs still rejects only the old protected port 8080, after which runBrowserRegression launches next dev --port 3000. The two processes then collide instead of the nightly runner failing closed during admission, which can invalidate local regression runs; migrate the protected-port check and its source-contract assertion together with this default.
Useful? React with 👍 / 👎.
This branch was successfully deployed
1 participant
Summary
47e9342b76c3203e58184e05b9cc06f256d867e9를 data로 올립니다.Test plan
Made with Cursor