Keyboard shortcuts order is not the same as treeview order

Describe the bug A bit of an edge case. When you create a new story for a component, it appears in the right place in treeview, but is treated as if it is at the very end as far as keyboard shortcuts are concerned.

Reproduction (via same kind in two files, kind of weird, but easy to repro):

1. Create three story files, A, B and C.
2. Make A + C’s stories both apply to the same kind.
3. In the UI A+C’s stories will be grouped.
4. However, keyboard shortcuts will apply in the order the stories are added; ie A -> B -> C

Reproduction (via HMR, more common):

1. Browse to a story in official storybook, e.g. “Placeholder > twoChildren”
2. Edit the story file, export a third story
3. Press “option + ->” (i.e. browse to next story). Notice it takes you to the next component
4. Click on the new story within the Placeholder.
5. Press “option + ->” (i.e. browse to next story). Notice nothing happens (it is treated as the last story)
6. Press “option + <-” (i.e. browse to prev story). Notice the very last story in the storybook is opened.

[tmeasday]

=> https://github.com/storybooks/storybook/pull/5805

[shilman]

Yo-ho-ho!! I just released https://github.com/storybooks/storybook/releases/tag/v5.0.0-rc.8 containing PR #5805 that references this issue. Upgrade today to try it out!

Because it’s a pre-release you can find it on the @next NPM tag.

Closing this issue. Please re-open if you think there’s still more to do.