Skip to content

Spike/base site approach c - #21855

Draft
sp94sap wants to merge 2 commits into
developfrom
spike/base-site-approach-c
Draft

Spike/base site approach c#21855
sp94sap wants to merge 2 commits into
developfrom
spike/base-site-approach-c

Conversation

@sp94sap

@sp94sap sp94sap commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

No description provided.

sp94sap added 2 commits August 7, 2026 12:38
…ED POC

Proves that BEFORE_APP_SERIALIZED cannot achieve clean text/plain transport
without the deprecated inject(RESPONSE) path. The HTML shell is always emitted
by CommonEngine and Content-Type cannot be set from inside the pipeline.

Resolution via AiSeoBaseSiteService (APP_INITIALIZER + ConfigInitializerService.
getStable('context')) works — zero extra OCC call. Transport does not.

Files:
- angular-native-base-site-service.ts: AiSeoBaseSiteService + provideAiSeoBaseSiteDetection()
- llms-txt.component.ts: LlmsTxtComponent + provideLlmsTxtRoute()
- app.config.server.ts: wires approach (c) providers
- server.ts: approach (c) only — Angular catch-all, no Express llms.txt handler
…er cut

/llms.txt reachable in Angular SSR — express.static fallthrough passes
dotted path to Angular catch-all. HTML shell from renderToString()
stripped post-render:

- LlmsTxtComponent: sets Content-Type via RESPONSE, wraps body in markers.
  Reads active baseSite via BaseSiteService.getActive() (toSignal) — proves
  per-site DI resolution in-pipeline.
- OptimizedSsrEngine: cuts body to marker content. Guarded by includes()
  check — normal renders untouched.
- server.ts: no functional change. Comments document fallthrough.
@sp94sap
sp94sap requested a review from a team as a code owner August 7, 2026 12:55
@github-actions
github-actions Bot marked this pull request as draft August 7, 2026 12:56
@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

🚨 PR Title Validation Failed 🚨

Your pull request title does not follow the required format. Please update it to match the expected pattern:

Expected format:
<type>: <subject>

Allowed Types

  • docs: Changes to documentation only
  • feat: New feature work
  • fix: Bug fixes
  • perf: Code improvements for performance
  • refactor: Code changes that are not bug fixes or features
  • style: Code style changes (e.g., whitespace, formatting)
  • test: Adding or updating tests
  • chore: Build, CI, scripts, configs, etc.

Example of a valid PR title

feat: Add user authentication
fix: Resolve checkout bug
docs: Update API documentation

Merge is blocked until the PR title is corrected.

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.

1 participant