Skip to content

Feat/merge conflict #161

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

Open
wants to merge 15 commits into
base: main
Choose a base branch
from
Open

Feat/merge conflict #161

wants to merge 15 commits into from

Conversation

5ewon
Copy link
Member

@5ewon 5ewon commented Apr 27, 2024

Issue Number

What

문서 충돌 발생시 해결하기 위한 컴포넌트를 구현했습니다.
추후 리팩터링 작업이 필수입니다~~
반복되는 코드에 대한 부분은 코멘트 달지 않으셔도 될듯합니다~~

How

ScreenShot

image
디자인 이슈는 요청시 해결될 수 있습니다. ux는 괜찮은거 아닐까요...?

@Ubinquitous Ubinquitous deleted the feat/mergeConflict branch November 15, 2024 16:26
@Ubinquitous Ubinquitous restored the feat/mergeConflict branch March 4, 2025 17:35
@Ubinquitous Ubinquitous reopened this Mar 4, 2025

try {
await merge({ title, contents: str, version: data.lastVersion });
toast(<Toastify content="출동이 해소되었습니다!" />);
Copy link

Choose a reason for hiding this comment

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

There appears to be a typo in the success message. The text 출동이 해소되었습니다! (which translates to "dispatch has been resolved") should be 충돌이 해소되었습니다! (which correctly translates to "conflict has been resolved").

Suggested change
toast(<Toastify content="출동이 해소되었습니다!" />);
toast(<Toastify content="충돌이 해소되었습니다!" />);

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

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.

2 participants