Skip to content

feat: check crew profile in partyroom#252

Open
YoonJongok wants to merge 13 commits intodevelopmentfrom
feat/PF-63-check-crew-info
Open

feat: check crew profile in partyroom#252
YoonJongok wants to merge 13 commits intodevelopmentfrom
feat/PF-63-check-crew-info

Conversation

@YoonJongok
Copy link
Contributor

@YoonJongok YoonJongok commented Feb 25, 2025

Summary

채팅 방에 다른 유저의 프로필 사진을 눌렀을 시 해당 유저의 프로필 정보를 볼 수 있습니다.

evidence

Todo

crew 정보 api에서 registrationDate가 추가되어야 합니다. 추가 확인 후 view-crew-profile.component.tsx: line 28의 nullish coalescing(??)을 제거해야 합니다.

Issue

N/A

Reference

N/A

@vercel
Copy link

vercel bot commented Feb 25, 2025

@YoonJongok is attempting to deploy a commit to the PFPlay team on Vercel, but is not a member of this team. To resolve this issue, you can:

  • Make your repository public. Collaboration is free for open source and public repositories.
  • Upgrade to pro and add @YoonJongok as a member. A Pro subscription is required to access Vercel's collaborative features.
    • If you're the owner of the team, click here to upgrade and add @YoonJongok as a member.
    • If you're the user who initiated this build request, click here to request access.
    • If you're already a member of the PFPlay team, make sure that your Vercel account is connected to your GitHub account.

To read more about collaboration on Vercel, click here.

@YoonJongok YoonJongok changed the title [WIP]Feat: PF-63 check crew info [WIP]Feat: PF-63 check crew profile in partyroom Feb 25, 2025
@YoonJongok YoonJongok changed the title [WIP]Feat: PF-63 check crew profile in partyroom Feat: PF-63 check crew profile in partyroom Feb 25, 2025
@will-kim-querypie will-kim-querypie changed the title Feat: PF-63 check crew profile in partyroom feat: check crew profile in partyroom Feb 25, 2025
Copy link
Contributor

@will-kim-querypie will-kim-querypie left a comment

Choose a reason for hiding this comment

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

처음 말씀드린대로 widget이 하나 만들어지고, 그 안에 동일 ui 프레임을 공유하는 my-profile-panel, crew-profile-panel 나뉘면 어떨까 싶습니다. profile은 entities에 두지 않구요, 컴포지션은 더 상위 레이어 (app) 에서 행하구요.

Comment on lines +5 to +6
import { Avatar } from '@/entities/avatar';
import { Profile } from '@/entities/profile';
Copy link
Contributor

@will-kim-querypie will-kim-querypie Feb 25, 2025

Choose a reason for hiding this comment

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

[변경요청]
의존성 방향이 역전됐습니다 shared -> entities

Comment on lines +22 to +25
export type CrewProfile = ProfileSummary & {
crewId: number;
registrationDate?: string;
};
Copy link
Contributor

Choose a reason for hiding this comment

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

[질문]
백단 dto에서 실제로 ProfileSummary라는 공통 필드 모음 dto 클래스를 따로 빼고 이를 확장하는 방식으로 사용하고 있나요? 아니면 그냥 중복되는 필드들이 보이니 ProfileSummary 라는 이름의 인터페이스로 분기하신 걸까요?
후자라면 인터페이스 확장 제거하고 각 dto를 따로 냅두는게 좋을 것 같습니다. 공용이라 생각하고 분리한게 사실 공용이 아닌 경우가 많더라구요.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

후자였습니다. 확장 제거하고 각 dto 따로 두겠습니다!

Comment on lines +4 to +23
export type Model = {
avatarBodyUri: string;
avatarFaceUri: string;
combinePositionX: number;
combinePositionY: number;
nickname: string;
introduction: string;
score: number;
registrationDate: string;
};

export const score = (activitySummaries: ActivitySummary[], activityType: ActivityType): number => {
const summary = activitySummaries.find((summary) => summary.activityType === activityType);

return summary ? summary.score : 0;
};

export const registrationDate = (registrationDate: string): string => {
return registrationDate.replace(/-/g, '.');
};
Copy link
Contributor

Choose a reason for hiding this comment

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

[변경요청]

  • 모델의 score와 computed score가 공존하고 있습니다.
  • computed score가 인자로 받는 값들은 이 모델이 가지고 있는 값이 아닙니다.

@Yeonny0723 Yeonny0723 requested a review from a team as a code owner February 19, 2026 14:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants