문제
런타임 문서가 MOCK·HTTP를 고르므로 두 소스가 모든 빌드에 들어간다.
기능 입력 조립(create-tech-log-feature-input.ts)이 MOCK 공개 콘텐츠,
MOCK·HTTP Studio gateway를 정적으로 가져와, 운영(HTTP) 공개 화면을
여는 사람도 그 코드를 초기 JS로 받았다. MOCK이 쓰는 content-format은
마크다운 파서(micromark·mdast·unified)까지 끌고 왔다. 초기 JS는 main
에서 300,869 B(gzip)로 예산 204,800 B를 넘는다(FE-GATE-012).
고른 방법
- 포트는 이미 모두 Promise를 돌려준다. deferAsyncPort가 포트를 먼저
만들고 첫 호출에서 구현 모듈을 동적 import해 넘긴다. 호출하는 쪽과
feature input의 모양(publicContent, createStudioApplication)은 그대로다.
- 포트 키 목록은 `Record<keyof Port, true>`로 적어, 포트에 메서드가
늘거나 줄면 타입 검사가 실패한다.
- 구현 받기에 실패하면 잊고 다음 호출에서 다시 받는다.
- MOCK 공개 콘텐츠는 첫 조회 때 받는다. HTTP 공개 gateway는 공개 첫
화면의 데이터 요청에 쓰이므로 그대로 둔다.
- Studio gateway 셋(MOCK이면 Studio state 하나를 나눠 씀)은 묶음 하나로
받는다(mock-studio-gateways.ts, http-studio-gateways.ts).
createStudioApplication은 Studio가 마운트될 때 불리므로 그때 바로 받기
시작한다(startNow). 첫 조회 때 받으면 화면 청크 → 조회 → gateway 청크
→ 요청으로 한 번 더 기다린다.
버린 대안
- createStudioApplication을 async로 바꾸기: StudioProvider와 시험 15곳이
함께 바뀐다. 포트가 이미 비동기라 필요 없다.
- 공개 HTTP gateway도 지연 로드: 첫 화면 데이터 요청 앞에 청크 왕복이
하나 생긴다.
위험·한계
- MOCK 빌드(로컬·e2e·visual)는 첫 공개 조회와 첫 Studio 조회 앞에 청크를
한 번 받는다.
- 포트 메서드가 동기 값을 돌려주게 바뀌면 이 방식은 맞지 않는다. 타입
제약(모든 멤버가 Promise를 돌려줌)이 그때 컴파일에서 막는다.
검증
- desktop CI env 빌드: 초기 JS 300,869 → 232,337 B(Studio 셸 지연을
포함한 측정, 다음 커밋). 빠진 모듈 179개 중 npm(마크다운 파서) 약
88 KB, mock 23 KB, static 11 KB(모듈 단독 gzip 합).
- tests/features/tech-log/deferred-async-port.test.ts: 한 번만 받기, 동시
첫 호출, 실패 뒤 다시 받기, 키·freeze, gateway 셋의 state 공유, startNow.
105 lines
4.5 KiB
TypeScript
105 lines
4.5 KiB
TypeScript
import {
|
|
TECH_LOG_FEATURE_ID,
|
|
type TechLogFeatureInput,
|
|
} from "../application/tech-log-feature-input.ts";
|
|
import type { Asset } from "../contracts/studio/contract.ts";
|
|
import { createTechLogStudioApplication } from "../application/studio-application.ts";
|
|
import type { InstalledHttpOperationExecutor } from "../../../adapters/http/index.ts";
|
|
import { createTechLogHttpBinding } from "./http/tech-log-http-binding.ts";
|
|
import type { CsrfTokenProvider } from "./http/studio-session-csrf.ts";
|
|
import { createHttpPublicContentGateway } from "./http/http-public-content-gateway.ts";
|
|
import {
|
|
deferPublicContentQueries,
|
|
deferStudioGateways,
|
|
} from "./deferred-tech-log-ports.ts";
|
|
|
|
/**
|
|
* The HTTP gateway builds no headers of its own — `Idempotency-Key` comes
|
|
* from the execution intent and credentials (including CSRF) come from the
|
|
* platform's `attachCredentials` collaborator at the composition root. This
|
|
* context only has to say which adapter to construct and hand it the
|
|
* composed contract executor.
|
|
*
|
|
* CSRF has exactly one provider per Studio session, owned by the composition
|
|
* root — it is shared with the platform's credential collaborator, so it is
|
|
* threaded in here rather than constructed locally.
|
|
*/
|
|
export type TechLogInstallContext = Readonly<{
|
|
studioSource: "MOCK" | "HTTP";
|
|
publicSource: "MOCK" | "HTTP";
|
|
http: InstalledHttpOperationExecutor;
|
|
apiBaseUrl: string;
|
|
requestTimeoutMs: number;
|
|
csrf: CsrfTokenProvider;
|
|
}>;
|
|
|
|
export function createTechLogFeatureInstalledInput(
|
|
context: TechLogInstallContext,
|
|
) {
|
|
// Fix round 1 (I2). MOCK `studioSource` has no real backend behind either
|
|
// gateway, so — unlike HTTP, where the real server is shared, external
|
|
// authority for both — the mock document gateway and a mock asset gateway
|
|
// must share ONE in-memory Asset store, or the mock's own `validateDocument`
|
|
// could never learn about an Asset the Picker just loaded/uploaded. This map
|
|
// is scoped to this one `createTechLogFeatureInstalledInput` call (the
|
|
// composition root calls it once per app instance), so every
|
|
// `createStudioGateway`/`createStudioAssetGateway` pair produced from this
|
|
// same `input` — across every `StudioProvider` mount over the app's
|
|
// lifetime — shares it, the same way a real backend's asset store outlives
|
|
// any one editing session. It is never read on the HTTP branch.
|
|
const mockAssets = new Map<string, Asset>();
|
|
const http = createTechLogHttpBinding(context.http);
|
|
|
|
// The public read source switches independently of Studio: the two are
|
|
// different services, and the combination that matters today is an authoring
|
|
// backend that is live while the public read API is not.
|
|
//
|
|
// FE-GATE-012. Both sources ship in every build (the runtime document picks
|
|
// one), so the MOCK content is loaded on its first query instead of riding
|
|
// the initial JavaScript of a production page that reads HTTP.
|
|
const publicContent =
|
|
context.publicSource === "MOCK"
|
|
? deferPublicContentQueries(
|
|
async () => (await import("./static/public-query.ts")).publicContentQueries,
|
|
)
|
|
: createHttpPublicContentGateway({ http });
|
|
|
|
// MOCK: one in-memory Studio state per application, shared by the document
|
|
// and management gateways, so deleting a draft from the management surface
|
|
// also takes it out of the document list. Management used to be HTTP even
|
|
// here, and a MOCK build (local development, the e2e and visual builds)
|
|
// asked an API that is not there for its topics and projects.
|
|
//
|
|
// FE-GATE-012. Studio's gateways, MOCK or HTTP, are a chunk of their own.
|
|
// StudioProvider calls this when Studio mounts, so the chunk starts loading
|
|
// then, next to the page chunk, rather than on the first query. Each call
|
|
// still gets its own set (and, for MOCK, its own state).
|
|
const createStudioApplication = () =>
|
|
createTechLogStudioApplication(
|
|
deferStudioGateways(
|
|
async () =>
|
|
context.studioSource === "MOCK"
|
|
? (await import("./mock/mock-studio-gateways.ts")).createMockStudioGateways(
|
|
mockAssets,
|
|
)
|
|
: (await import("./http/http-studio-gateways.ts")).createHttpStudioGateways({
|
|
http,
|
|
csrf: context.csrf,
|
|
apiBaseUrl: context.apiBaseUrl,
|
|
requestTimeoutMs: context.requestTimeoutMs,
|
|
}),
|
|
{ startNow: true },
|
|
),
|
|
);
|
|
|
|
const input: TechLogFeatureInput = Object.freeze({
|
|
publicContent,
|
|
createStudioApplication,
|
|
});
|
|
|
|
return Object.freeze({
|
|
featureId: TECH_LOG_FEATURE_ID,
|
|
input,
|
|
});
|
|
}
|