-
-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(dev): remove dependency on resolve order for linking in markdown … #599
Conversation
…files This fixes the error when linking a markdown file to another markdown file that is higher than the resolve order of the parent. histoire-dev#562
Run & review this pull request in StackBlitz Codeflow. |
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
✅ Deploy Preview for histoire-examples-vue3 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for histoire-site ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for histoire-controls ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for histoire-examples-svelte3 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Thanks for the PR! Looks like build is failing though |
Apologies I must have forgot to run the build. I have pushed another commit with the required changes. This is currently building for me but if there are any other issues or concerns, please let me know. |
Looking good, thanks! |
This fixes the error when linking a markdown file to another markdown file that is higher than the resolve order of the parent.
#562
Description
This PR focuses on removing the dependency on the resolve order when linking markdown files, where this would previously throw an "Error: [md] Cannot find story file" exception when the resolve order was out of sync, this PR now allows for out-of-resolve order linking.
Additional context
Whether this will impact performance on larger projects by looping through Markdown files once the watcher is complete.
Some changes had to be made to the
tree.spec
file for the tests to pass. Not sure if this is done correctly or if my tests are in the right place (markdown.spec
)What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123
).