Skip to content
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

Core: Fix configFilename containing backticks #9960

Merged
merged 1 commit into from
Feb 26, 2020
Merged

Core: Fix configFilename containing backticks #9960

merged 1 commit into from
Feb 26, 2020

Conversation

tmeasday
Copy link
Member

@tmeasday tmeasday commented Feb 26, 2020

Issue: #9937

In windows the path sep is \ which will lead to weird stuff like: chromaui/learnstorybook.com#284

In windows the path sep is '\' which will lead to weird stuff like: chromaui/learnstorybook.com#284
@github-actions
Copy link
Contributor

Fails
🚫

PR is not labeled with one of: ["cleanup","doc-dependencies:update","BREAKING CHANGE","feature request","bug","documentation","maintenance","dependencies:update","dependencies","other"]

Generated by 🚫 dangerJS against 20920b5

@shilman shilman added bug core patch:yes Bugfix & documentation PR that need to be picked to main branch labels Feb 26, 2020
Copy link
Member

@shilman shilman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@shilman shilman changed the title Fix configFilename containing backticks Core: Fix configFilename containing backticks Feb 26, 2020
@shilman shilman removed the patch:yes Bugfix & documentation PR that need to be picked to main branch label Feb 26, 2020
@shilman shilman added this to the 6.0.0 milestone Feb 26, 2020
@shilman
Copy link
Member

shilman commented Feb 26, 2020

@tmeasday this looks like 6.0 code. does it also need to get patched to 5.3?

@shilman shilman merged commit 2b8e15b into next Feb 26, 2020
@shilman shilman deleted the Fix-LSB-284 branch February 26, 2020 12:32
@tmeasday
Copy link
Member Author

No, was just a fix to the parameter refactor stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants