docs(search): explore facets·sort 백엔드 계약 (#842)#869
Draft
thxforall wants to merge 1 commit into
Draft
Conversation
meili posts 인덱스는 이미 solution_count sortable + facet 축 filterable로 구성됨(index_config.rs). 진짜 갭은 advanced_search의 with_facets 배선 + service.rs의 Facets None 하드코딩 제거. FE 응답 계약(facets shape·sort vocab·post-filter count)은 backend-무관이라 지금 확정 → #851 언블록. browse(DB) facet/정렬 구현 옵션(meili 통합 vs DB 집계)은 philippe 비준 대기 → #842 OPEN 유지. Co-Authored-By: Claude Opus 4.8 <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
무엇 / 왜
#842 (계약·설계 슬라이스)의 산출물 — explore facets + sort 백엔드 계약을 실제 코드 현황에 근거해 문서화.
docs/architecture/explore-facets-sort-contract.md신규.Part of #842 · PRD #825 · map #789 · #851 관계 = FE 스캐폴딩을 고정 shape에 대고 착수 가능(단, #851 AC 통과는 서버 구현 랜딩 후)
Load-bearing 발견 (스코프 재조정)
"meili faceting 프로젝트"가 아님 — 인덱스는 이미 구성돼 있음:
index_config.rs:POSTS_SORTABLE에solution_count有,POSTS_FILTERABLE에 facet 축(category_codes/context/media_type) 有solution_count정렬은 이미/search에서 동작 (search/service.rs:66)advanced_search가with_facets미호출 +service.rs:153-159가Facets를 None 하드코딩문서 구성
solution_count승격),facetsshape 고정, facet count = post-filter 시맨틱 픽스style_tags서버 필터)는 미색인 + Style DNA 택소노미 SSOT + 9무드 탭 + T10 drift CI #849(Style DNA SSOT) 의존 → 별도 처리 플래그AC 매핑 (#842)
#851 영향 (정확히)
이 계약은 #851의 FE 스캐폴딩을 고정된 응답 shape에 대고 시작하게 해줌. 단 #851의 3개 AC(서버 facet distribution 반영·
solution_count서버 정렬·style_tags서버 필터)는 모두 아직 없는 백엔드를 요구하며 philippe 구현 랜딩 후에야 통과 가능. 즉 #851은 "착수 가능"이지 "실행 준비 완료"가 아님.검증
bump:none). 코드 변경 없음 → 빌드/테스트 무관.philippe 확인 질문
solution_count정렬 소스(집계 컬럼 vs 조인)?style_tags필터는 익스플로어 필터 graduated (서버 facet/sort) #851 포함 vs Style DNA 택소노미 SSOT + 9무드 탭 + T10 drift CI #849 이후 별도?🤖 Generated with Claude Code