채팅별 과거 채팅조회 (역방향) api 병합실수로 인한 추가 병합

[bo-ram-bo-ram]

Pull request

Related issue

#226
#225

Motivation and context

• 제가 be-feat/history-forward-api 브랜치에서 정방향 api를 구현하고 역방향 구현 시 정방향 코드가 필요해서 be-feat/history-forward-api 브랜치에서 be-feat/history-backward-api 브랜치를 파고 타겟을 be-feat/history-forward-api 로 해서 pr을 날렸는데 병합도 be-feat/history-forward-api 로 잘못했습니다.

Solution

• be-feat/history-forward-api 에서 dev로 추가 병합을 진행합니다.

How has this been tested

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the docs/CONTRIBUTING.md document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[netlify]

✅ Deploy Preview for jootalkpia canceled.

Name	Link
🔨 Latest commit	3da1f74
🔍 Latest deploy log	https://app.netlify.com/sites/jootalkpia/deploys/67b99bb1a1229800088ca3c3