Preview: Handle new docs-page index entries

[tmeasday]

Telescoping on #18574

Handle new docs entries types in the preview. In particular:

• No longer allow rendering stories in docs mode
• Refactor things a little for clarity (separate the two types of "docs render")
• When rendering a "template" docs entry (attached to a story file), ensure we all the referenced CSF files (from storyImports also), to account for multiple files that define stories for the same component.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 79e5367. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 1 target

• nx run-many --target=prepare --all --parallel=8 --max-parallel=15 -- --reset --optimized

---

Sent with 💌 from NxCloud.

[tmeasday]

@shilman As you predicted the e2e-tests-sb-docs don't make any sense any more as they are testing each story in "docs" mode, which is no longer a real thing. We'll need to adjust the test runner to actually test docs entries I guess if we want to test docs in the runner.

What should I do with that for now? I'll disable the whole circle task, but if you think something different, let me know.

[tmeasday]

@ndelangen why did you make this a draft?

[shilman]

Why is this PossibleRender and not just Render? PossibleRender sounds like there may or may not actually be a render...

[tmeasday]

Render is the name of the interface. I could change that to BaseRender?

[shilman]

IRender? BaseRender sounds like it's providing some base functionality but it's just an interface. I wonder what's idiomatic TypeScript for this? I'm very familiar with this pattern from my OO days, but I haven't seen the analog to PossibleRender there.

[tmeasday]

I can't really remember what it was like to code in an OO language but I think TS does stuff with type "elimination" that I don't recall from those days. Like if you have const x: A | B and then put if (x not of type A) in your code (that's pseudo code) TS will automatically cast it to B which is super handy.

Whereas if you have const x: I where I is an interface that A and B implement, it can't know that x isn't so other theoretical implementer, even if none exist.