Repository: portone-io/developers.portone.io
Pull request #870: 250519 OPI 릴리즈노트 추가
Author: login: Deea222
Created: 2025-05-19T03:25:03Z | Merged: 2025-05-20T03:36:30Z

https://www.notion.so/portone/OPI-05-19-1f5e64345c3180e49dcef1c697cf968c


Diff:
diff --git a/src/routes/(root)/release-notes/(note)/api-sdk/2025-05-19.mdx b/src/routes/(root)/release-notes/(note)/api-sdk/2025-05-19.mdx
new file mode 100644
index 000000000..b48b6eb9f
--- /dev/null
+++ b/src/routes/(root)/release-notes/(note)/api-sdk/2025-05-19.mdx
@@ -0,0 +1,60 @@
+---
+releasedAt: 2025-05-19
+writtenAt: 2025-05-19
+---
+
+import Figure from "~/components/Figure";
+import { prose } from "~/components/prose";
+import { Console } from "~/components/release-note/badges";
+
+import Image0 from "./_assets/2025-05-19/image0.png";
+import Image1 from "./_assets/2025-05-19/image1.png";
+import Image2 from "./_assets/2025-05-19/image2.png";
+import Image3 from "./_assets/2025-05-19/image3.png";
+
+안녕하세요 원 페이먼트 인프라팀입니다. 25년 5월 19일, 서비스 업데이트 사항 안내드립니다.
+
+이번 업데이트를 통해 통합 결제 내역 페이지가 새롭게 탈바꿈을 했습니다.
+
+개선 작업은 아래와 같습니다.
+
+<prose.h3>
+  <Console />
+</prose.h3>
+
+## 주요 업데이트 사항
+
+### ✔️ 캘린더 UI 고도화
+
+<Figure src={Image0} caption="캘린더 UI 고도화" />
+
+- 상태 승인 시각, 결제 요청 시각을 기준으로 원하는 날짜를 쉽게 조회할 수 있습니다.
+  - 시작일과, 종료일을 직접 입력하거나 캘린더에서 일자를 선택하여 날짜를 조회할 수 있습니다.
+  - “오늘”, “어제”, “1주”, “1개월”, “3개월”, “6개월” 의 프리셋을 활용하여 직접 입력하지 않고도 간편하게 일자를 설정할 수 있습니다.
+
+### ✔️ 검색 조건 최적화
+
+<Figure src={Image1} caption="검색 조건 최적화" />
+
+- 검색을 쉽게 할 수 있도록 각 검색 조건마다 최적화 작업을 진행하였습니다.
+  - 주문 정보
+    - 주문자명, 주문자 연락처, 주문명, 주문자 이메일, 주문자 주소로 더욱 정교화된 검색을 할 수 있습니다.
+
+  - 거래번호
+    - 포트원 거래번호, 고객사 거래번호를 동시에 검색할 수 있습니다.
+
+  - 승인번호
+    - 카드사 승인번호, 결제대행사 승인번호, PG결제취소 승인번호를 동시에 검색할 수 있습니다.
+
+### ✔️ 필터 최적화
+
+<Figure src={Image2} caption="필터 최적화" />
+
+- 테이블 UI를 고도화함에 따라 테이블 헤더에 필터, 정렬 버튼이 추가되어 빠른 적용이 가능합니다.
+  - Tip) 실 운영 업무를 위해 결제 모드는 “실결제”로 필터가 기본 적용되어 있습니다. 테스트 결제 건을 확인하고 싶으시다면 결제 모드 필터를 해제해 주세요.
+
+### ✔️ 결제 히스토리 파악 가능
+
+<Figure src={Image3} caption="결제 히스토리 파악 가능" />
+
+- 기존에는 결제 상세 모달에서만 히스토리를 확인 가능했다면, 이제는 결제 내역에서 바로 확인할 수 있게 되었습니다. 결제 히스토리를 쉽게 확인하고 운영 업무에 활용하실 수 있습니다.
diff --git a/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image0.png b/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image0.png
new file mode 100644
index 000000000..51f3328a9
Binary files /dev/null and b/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image0.png differ
diff --git a/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image1.png b/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image1.png
new file mode 100644
index 000000000..807c12aff
Binary files /dev/null and b/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image1.png differ
diff --git a/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image2.png b/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image2.png
new file mode 100644
index 000000000..ac6397053
Binary files /dev/null and b/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image2.png differ
diff --git a/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image3.png b/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image3.png
new file mode 100644
index 000000000..ebdcefd8d
Binary files /dev/null and b/src/routes/(root)/release-notes/(note)/api-sdk/_assets/2025-05-19/image3.png differ


Reviews:
user: login: windsurf-bot[bot]
state: COMMENTED
author_association: NONE
submitted_at: 2025-05-19T03:25:24Z
user: login: gemini-code-assist[bot]
body: Hello @Deea222, I'm Gemini Code Assist[^1]! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

## Summary of Changes
Hello, gemini-code-assist here. I've reviewed this pull request. The primary goal of this PR, based on the title and patch content, is to add a new release note document for May 19, 2025. This document specifically details recent updates made to the unified payment history page.

### Highlights
* **New Release Note Document**: This PR introduces a new release note file (`2025-05-19.mdx`) to the documentation, outlining service updates.
* **Unified Payment History Page Updates**: The release notes detail several improvements to the unified payment history page, including enhancements to the calendar UI, optimization of search conditions, improved filtering capabilities, and making payment history directly visible in the list.
* **Calendar UI Enhancement**: The calendar UI has been upgraded to allow easier date selection based on approval/request time, with options for direct input, calendar picking, and preset ranges (Today, Yesterday, 1 week, 1, 3, 6 months).
* **Search Condition Optimization**: Search functionality is refined for various criteria, enabling more precise searches for order information (name, contact, name, email, address), simultaneous search for PortOne/customer transaction IDs, and combined search for card/PG/PG cancellation approval numbers.
* **Filter Optimization**: Filters and sort buttons are now integrated into the table header for quicker application. A default filter for 'real payment' is applied for operational efficiency, with instructions on how to view test payments.
* **Payment History Visibility**: Payment history is now directly accessible within the main payment history list view, removing the need to open a separate detail modal to see the history.

### Changelog
* **src/routes/(root)/release-notes/(note)/api-sdk/2025-05-19.mdx**
  * Added a new MDX file containing the release notes for the May 19, 2025 service update.
  * The content describes improvements to the unified payment history page, including calendar UI, search, filter, and payment history visibility enhancements.


<details>

<summary><b>Using Gemini Code Assist</b></summary>
<br>

The full guide for Gemini Code Assist can be found on our [documentation page](https://developers.google.com/gemini-code-assist/docs/review-github-code), here are some quick tips.

<b>Invoking Gemini</b>

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either `/gemini <command>` or `@gemini-code-assist <command>`. Below is a summary of the supported commands.

Feature | Command | Description
--- | --- | ---
Code Review | `/gemini review` | Performs a code review for the current pull request in its current state.
Pull Request Summary | `/gemini summary` | Provides a summary of the current pull request in its current state.
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments.
Help | `/gemini help` | Displays a list of available commands.

<b>Customization</b>

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a `.gemini/` folder in the base of the repository. Detailed instructions can be found [here](https://developers.google.com/gemini-code-assist/docs/customize-gemini-behavior-github).

<b>Limitations & Feedback</b>

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with :thumbsup: and :thumbsdown: on @gemini-code-assist comments to provide feedback.

</details>

<b>You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the [Gemini Code Assist IDE Extension](https://cloud.google.com/products/gemini/code-assist).</b>


[^1]: Review the [Privacy Notices](https://policies.google.com/privacy), [Generative AI Prohibited Use Policy](https://policies.google.com/terms/generative-ai/use-policy), [Terms of Service](https://policies.google.com/terms), and learn how to configure Gemini Code Assist in GitHub [here](https://developers.google.com/gemini-code-assist/docs/review-github-code). Gemini can make mistakes, so double check it and [use code with caution](https://support.google.com/legal/answer/13505487).

---

> New notes arrive now,
> Payment history updates,
> Docs make work clear.


state: COMMENTED
author_association: NONE
submitted_at: 2025-05-19T03:25:24Z
user: login: gemini-code-assist[bot]
body: ## Code Review
This pull request introduces a new release note for the OPI (One Payment Infrastructure) updates scheduled for May 19, 2025. The content is well-detailed, covering several enhancements to the admin console, including UI improvements for calendars, search, filters, and payment history visibility, complete with illustrative images.

Overall, the structure and content are good. However, there are a few areas for improvement, primarily concerning web accessibility (image alt text), semantic HTML (heading order), and markdown formatting consistency. Addressing these will significantly enhance the quality and user experience of the release note.

Since no specific style guide was provided, my review is based on general best practices for Markdown, HTML semantics, and web accessibility (WCAG guidelines).

### Summary of Findings
* **Accessibility: Missing Image Alt Text**: Images are used via the `Figure` component without a `caption` prop, leading to empty `alt` attributes. This is a high-severity accessibility issue as it prevents screen reader users from understanding image content. (Lines 29, 37, 49, 56)
* **Semantic HTML: Incorrect Heading Order**: The document structure uses an H3 heading followed by an H2 heading (lines 21-25), which is semantically incorrect and can negatively impact accessibility and SEO. Headings should be in a logical descending order.
* **Markdown Formatting: Tip Presentation**: A 'Tip)' is formatted as plain text within a list item (line 52), which reduces its prominence. Using blockquote formatting would improve its visibility and semantic distinction.
* **Content: Future Dates**: The `releasedAt` and `writtenAt` dates in the frontmatter (lines 2-3) are set to `2025-05-19`. This is likely intentional for a future release but noted for awareness. (Not commented due to review settings)
* **Formatting: Missing Newline at End of File**: The file `src/routes/(root)/release-notes/(note)/api-sdk/2025-05-19.mdx` is missing a newline character at the end of the file (line 58). This is a minor formatting/linting issue. (Not commented due to review settings)

### Merge Readiness
This pull request adds a new release note for the OPI updates. The content is informative and covers several enhancements. However, there are a few important areas that need attention before merging to ensure accessibility and proper document structure:

*   **Critical for Accessibility:** Images are missing alternative text. This must be addressed.
*   **Semantic Structure:** The heading order (H3 followed by H2) should be corrected.
*   **Readability:** The formatting of the 'Tip' can be improved.

Addressing these points will significantly enhance the quality and accessibility of the release note. While I am unable to approve the pull request directly, I strongly recommend that these changes be implemented before it is merged. Other reviewers should also assess these changes.
state: CHANGES_REQUESTED
author_association: NONE
submitted_at: 2025-05-19T03:32:43Z
user: login: CirnoV
state: APPROVED
author_association: MEMBER
submitted_at: 2025-05-19T03:36:07Z

Review comments:
diff_hunk: @@ -0,0 +1,58 @@
+---
+releasedAt: 2025-05-19
+writtenAt: 2025-05-19
path: src/routes/(root)/release-notes/(note)/api-sdk/2025-05-19.mdx
user: login: windsurf-bot[bot]
body: The release date is set to 2025-05-19, which is a future date. Please verify if this is intentional or if the date should be corrected to a current/past date.
created_at: 2025-05-19T03:25:23Z
author_association: NONE
diff_hunk: @@ -0,0 +1,58 @@
+---
+releasedAt: 2025-05-19
+writtenAt: 2025-05-19
+---
+
+import Figure from "~/components/Figure";
+import { prose } from "~/components/prose";
+import { Console } from "~/components/release-note/badges";
+
+import Image0 from "./_assets/2025-05-19/image0.png";
+import Image1 from "./_assets/2025-05-19/image1.png";
+import Image2 from "./_assets/2025-05-19/image2.png";
+import Image3 from "./_assets/2025-05-19/image3.png";
+
+안녕하세요 원 페이먼트 인프라팀입니다. 25년 5월 19일, 서비스 업데이트 사항 안내드립니다.
+
+이번 업데이트를 통해 통합 결제 내역 페이지가 새롭게 탈바꿈을 했습니다.
+
+개선 작업은 아래와 같습니다.
+
+<prose.h3>
+  <Console />
+</prose.h3>
+
+## 주요 업데이트 사항
path: src/routes/(root)/release-notes/(note)/api-sdk/2025-05-19.mdx
user: login: gemini-code-assist[bot]
body: ![medium](https://img.shields.io/badge/priority-medium-yellow)

The current heading structure presents `<prose.h3><Console /></prose.h3>` (which renders an `<h3>` containing '관리자 콘솔') followed by `## 주요 업데이트 사항` (an `<h2>`). This H3 -> H2 sequence is semantically incorrect. For proper document structure and accessibility, headings should follow a logical, descending order (e.g., H1 -> H2 -> H3).

If '관리자 콘솔' is the main section and '주요 업데이트 사항' are subsections within it, could we adjust the heading levels accordingly? For instance, making '관리자 콘솔' an `<h2>` and '주요 업데이트 사항' an `<h3>` would create a more logical flow.

```
<prose.h2>
  <Console />
</prose.h2>

### 주요 업데이트 사항
```
created_at: 2025-05-19T03:32:43Z
author_association: NONE
diff_hunk: @@ -0,0 +1,58 @@
+---
+releasedAt: 2025-05-19
+writtenAt: 2025-05-19
+---
+
+import Figure from "~/components/Figure";
+import { prose } from "~/components/prose";
+import { Console } from "~/components/release-note/badges";
+
+import Image0 from "./_assets/2025-05-19/image0.png";
+import Image1 from "./_assets/2025-05-19/image1.png";
+import Image2 from "./_assets/2025-05-19/image2.png";
+import Image3 from "./_assets/2025-05-19/image3.png";
+
+안녕하세요 원 페이먼트 인프라팀입니다. 25년 5월 19일, 서비스 업데이트 사항 안내드립니다.
+
+이번 업데이트를 통해 통합 결제 내역 페이지가 새롭게 탈바꿈을 했습니다.
+
+개선 작업은 아래와 같습니다.
+
+<prose.h3>
+  <Console />
+</prose.h3>
+
+## 주요 업데이트 사항
+
+### ✔️ 캘린더 UI 고도화
+
+<Figure src={Image0} />
+
+- 상태 승인 시각, 결제 요청 시각을 기준으로 원하는 날짜를 쉽게 조회할 수 있습니다.
+  - 시작일과, 종료일을 직접 입력하거나 캘린더에서 일자를 선택하여 날짜를 조회할 수 있습니다.
+  - “오늘”, “어제”, “1주”, “1개월”, “3개월”, “6개월” 의 프리셋을 활용하여 직접 입력하지 않고도 간편하게 일자를 설정할 수 있습니다.
+
+### ✔️ 검색 조건 최적화
+
+<Figure src={Image1} />
+
+- 검색을 쉽게 할 수 있도록 각 검색 조건마다 최적화 작업을 진행하였습니다.
+  - 주문 정보
+    - 주문자명, 주문자 연락처, 주문명, 주문자 이메일, 주문자 주소로 더욱 정교화된 검색을 할 수 있습니다.
+  - 거래번호
+    - 포트원 거래번호, 고객사 거래번호를 동시에 검색할 수 있습니다.
+  - 승인번호
+    - 카드사 승인번호, 결제대행사 승인번호, PG결제취소 승인번호를 동시에 검색할 수 있습니다.
+
+### ✔️ 필터 최적화
+
+<Figure src={Image2} />
+
+- 테이블 UI를 고도화함에 따라 테이블 헤더에 필터, 정렬 버튼이 추가되어 빠른 적용이 가능합니다.
+  - Tip) 실 운영 업무를 위해 결제 모드는 “실결제”로 필터가 기본 적용되어 있습니다. 테스트 결제 건을 확인하고 싶으시다면 결제 모드 필터를 해제해 주세요.
path: src/routes/(root)/release-notes/(note)/api-sdk/2025-05-19.mdx
user: login: gemini-code-assist[bot]
body: ![medium](https://img.shields.io/badge/priority-medium-yellow)

The 'Tip)' on this line is presented as plain text within a sub-list item. To enhance its visibility and semantic meaning as a distinct piece of advice, would it be possible to format it using Markdown's blockquote syntax? This would make the tip stand out more clearly from the regular content.

```
  - > **Tip:** 실 운영 업무를 위해 결제 모드는 “실결제”로 필터가 기본 적용되어 있습니다. 테스트 결제 건을 확인하고 싶으시다면 결제 모드 필터를 해제해 주세요.
```
created_at: 2025-05-19T03:32:43Z
author_association: NONE

PR comments:
user: login: vercel[bot]
created_at: 2025-05-19T03:25:08Z
body: [vc]: #Yy5ojApVS005/FqRukK45yEDRvCrzFEWjnrYbUNDorw=:eyJpc01vbm9yZXBvIjp0cnVlLCJ0eXBlIjoiZ2l0aHViIiwicHJvamVjdHMiOlt7Im5hbWUiOiJkZXZlbG9wZXJzIiwiaW5zcGVjdG9yVXJsIjoiaHR0cHM6Ly92ZXJjZWwuY29tL3BvcnRvbmUvZGV2ZWxvcGVycy9DQThtWGRlSk5uSkU0UjQ5NkZUVVZzV3h1b3diIiwicHJldmlld1VybCI6ImRldmVsb3BlcnMtZ2l0LXVwZGF0ZS1ub3RlLTI1MDUxOS1wb3J0b25lLnZlcmNlbC5hcHAiLCJuZXh0Q29tbWl0U3RhdHVzIjoiREVQTE9ZRUQiLCJsaXZlRmVlZGJhY2siOnsicmVzb2x2ZWQiOjAsInVucmVzb2x2ZWQiOjAsInRvdGFsIjowLCJsaW5rIjoiZGV2ZWxvcGVycy1naXQtdXBkYXRlLW5vdGUtMjUwNTE5LXBvcnRvbmUudmVyY2VsLmFwcCJ9LCJyb290RGlyZWN0b3J5IjpudWxsfV19
**The latest updates on your projects**. Learn more about [Vercel for Git ↗︎](https://vercel.link/github-learn-more)

| Name | Status | Preview | Comments | Updated (UTC) |
| :--- | :----- | :------ | :------- | :------ |
| **developers** | ✅ Ready ([Inspect](https://vercel.com/portone/developers/CA8mXdeJNnJE4R496FTUVsWxuowb)) | [Visit Preview](https://developers-git-update-note-250519-portone.vercel.app) | 💬 [**Add feedback**](https://vercel.live/open-feedback/developers-git-update-note-250519-portone.vercel.app?via=pr-comment-feedback-link) | May 20, 2025 3:53am |


author_association: NONE
user: login: sonarqubecloud[bot]
created_at: 2025-05-20T03:35:28Z
body: ## [![Quality Gate Passed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/QualityGateBadge/qg-passed-20px.png 'Quality Gate Passed')](https://sonarcloud.io/dashboard?id=portone-io_developers.portone.io&pullRequest=870) **Quality Gate passed**  
Issues  
![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/passed-16px.png '') [0 New issues](https://sonarcloud.io/project/issues?id=portone-io_developers.portone.io&pullRequest=870&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true)  
![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/accepted-16px.png '') [0 Accepted issues](https://sonarcloud.io/project/issues?id=portone-io_developers.portone.io&pullRequest=870&issueStatuses=ACCEPTED)

Measures  
![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/passed-16px.png '') [0 Security Hotspots](https://sonarcloud.io/project/security_hotspots?id=portone-io_developers.portone.io&pullRequest=870&issueStatuses=OPEN,CONFIRMED&sinceLeakPeriod=true)  
![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/passed-16px.png '') [0.0% Coverage on New Code](https://sonarcloud.io/component_measures?id=portone-io_developers.portone.io&pullRequest=870&metric=new_coverage&view=list)  
![](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/common/passed-16px.png '') [0.0% Duplication on New Code](https://sonarcloud.io/component_measures?id=portone-io_developers.portone.io&pullRequest=870&metric=new_duplicated_lines_density&view=list)  
  
[See analysis details on SonarQube Cloud](https://sonarcloud.io/dashboard?id=portone-io_developers.portone.io&pullRequest=870)


author_association: NONE