Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(community): 공지사항 상세글 페이지 #45

Merged
merged 13 commits into from
Dec 9, 2024

Conversation

SunwooJaeho
Copy link
Member

@SunwooJaeho SunwooJaeho commented Dec 7, 2024

Summary

resolved #40

공지사항 상세글 페이지 퍼블리싱을 했어요.

Tasks

  • 공지사항 상세글 페이지 퍼블리싱

To Reviewer

모든 상세글 페이지의 디자인을 해당 레이아웃과 동일하게 해도 좋을 지에 대한 의견이 궁금합니다!
(최소한 학부 소식은 동일 레이아웃으로 가는 걸 고민 중입니다!)

Screenshot

image

footer를 추가하였어요.

@SunwooJaeho SunwooJaeho added the enhancement New feature or request label Dec 7, 2024
@SunwooJaeho SunwooJaeho self-assigned this Dec 7, 2024
@SunwooJaeho SunwooJaeho linked an issue Dec 7, 2024 that may be closed by this pull request
1 task
Copy link
Contributor

coderabbitai bot commented Dec 7, 2024

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Comment on lines +47 to +49
function Content({ content }: { content: string }) {
return <div className={styles.content}>{content}</div>;
}
Copy link
Member

Choose a reason for hiding this comment

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

Content의 content는 Render Props 패턴으로 되어 있는데 의도하신 이유가 있나요? children이 더 적절해보이는데 특별한 이유가 있는지 궁금합니다.

Copy link
Member Author

Choose a reason for hiding this comment

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

현재 목데이터로 swagger의 예시 데이터를 사용하고 있는데요, 저도 children이 더 적절하다고 생각하였으나 해당 목데이터의 content가 노드가 아닌 단순 string 값으로 설정되어 있어 render props로 렌더링 중입니다! 혹시 적절한 방법이 있을까요?

@gwansikk
Copy link
Member

gwansikk commented Dec 8, 2024

모든 상세글 페이지의 디자인을 해당 레이아웃과 동일하게 해도 좋을 지에 대한 의견이 궁금합니다!

일관적인 디자인을 가져가는게 좋다고 생각해요. 일단은. 나중에 다르게 해야할 특별한 요구사항이 있다면 그때 변경하는것으로 해요.

추가로 기존에는 다음글 이전글과 같이 하단에 네비게이터도 있는데요. 해당 페이지는 너무 심플하다고 생각해요. 다른 레퍼런스도 찾아보면서 조금 완성도를 높여보는 건 어떨까요?

image

@SunwooJaeho SunwooJaeho requested a review from a team as a code owner December 8, 2024 16:09
@SunwooJaeho
Copy link
Member Author

모든 상세글 페이지의 디자인을 해당 레이아웃과 동일하게 해도 좋을 지에 대한 의견이 궁금합니다!

일관적인 디자인을 가져가는게 좋다고 생각해요. 일단은. 나중에 다르게 해야할 특별한 요구사항이 있다면 그때 변경하는것으로 해요.

추가로 기존에는 다음글 이전글과 같이 하단에 네비게이터도 있는데요. 해당 페이지는 너무 심플하다고 생각해요. 다른 레퍼런스도 찾아보면서 조금 완성도를 높여보는 건 어떨까요?

image

적극 동의합니다! 현재 상태에서 추가할 수 있는 기능을 고려해볼게요😊

@SunwooJaeho
Copy link
Member Author

SunwooJaeho commented Dec 8, 2024

모든 상세글 페이지의 디자인을 해당 레이아웃과 동일하게 해도 좋을 지에 대한 의견이 궁금합니다!

일관적인 디자인을 가져가는게 좋다고 생각해요. 일단은. 나중에 다르게 해야할 특별한 요구사항이 있다면 그때 변경하는것으로 해요.
추가로 기존에는 다음글 이전글과 같이 하단에 네비게이터도 있는데요. 해당 페이지는 너무 심플하다고 생각해요. 다른 레퍼런스도 찾아보면서 조금 완성도를 높여보는 건 어떨까요?
image

적극 동의합니다! 현재 상태에서 추가할 수 있는 기능을 고려해볼게요😊

"목록으로 돌아가기" 버튼을 추가하였어요!

@gwansikk
Copy link
Member

gwansikk commented Dec 9, 2024

@SunwooJaeho 이전글이나 다음글 등 다른 포스트 네이게이터를 추가할 계획은 없나요?

@SunwooJaeho
Copy link
Member Author

@SunwooJaeho 이전글이나 다음글 등 다른 포스트 네이게이터를 추가할 계획은 없나요?

현재 api 상에서는 이전글과 다음글에 대한 정보를 불러오지 않아 어떤 방식으로 구현하면 좋을 지 고민 중입니다! 따라서 현재는 목록으로 돌아가는 버튼만 추가해두었어요😄

@SunwooJaeho SunwooJaeho merged commit 2d29c1d into develop Dec 9, 2024
3 checks passed
@SunwooJaeho SunwooJaeho deleted the feature/notice-detail-page branch December 9, 2024 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature]: 공지사항 디테일 페이지
3 participants