Addon-docs: DocsPage story order should match the index

[tmeasday]

Issue: #17611

What I did

Ensure store.componentStoriesFromCSFFile() returns stories in the same order as the index

How to test

• Is this testable with Jest or Chromatic screenshots?
• Does this need a new example in the kitchen sink apps?
• Does this need an update to the documentation?

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit f19c992. 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 --max-parallel=15 -- --optimized

---

Sent with 💌 from NxCloud.

[shilman]

Nice one! LGTM 💯

[himerus]

Still seeing this issue after updated to the latest.

Example

• https://outline.phase2tech.com/?path=/docs/content-alert--information
• https://github.com/phase2/outline/blob/next/src/components/base/outline-alert/outline-alert.stories.ts

[tmeasday]

@himerus I'm a little confused -- it looks like the order in the linked build is the same as the order in the story file:

[himerus]

@tmeasday Sorry for the confusion or lack of clarification.

• Yes, the sidebar ordering of the Stories matches the order in the Story file.
• However, the actual Docs PAGE content is what is out of order in that example page.
  • Note the Information Story is down near the middle of the page, and the Error Story appears first (alphabetical).

My apologies if this is unrelated, or two separate issues based on the code that controls each.

[himerus]

Well, heck. Now that I re-post that issue, it appears that our "production" Storybook instance is properly updated, and now they DO in fact appear in order.

Please disregard my nonsense.

Thank for getting this resolved! It has been an annoyance for quite some time on our builds!!

[tmeasday]

No worries @himerus I have to say you had me really confused again for a second there! But I am glad the issue is fixed in either case. I guess you were previously running into this bug and now it is fixed so the end result is a good one.