Uh oh!
There was an error while loading. Please reload this page.
fix: allow also " inside of an embed - #1598
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/docsify-core/docsify-preview/BJiGEnyE33rV1Pzk3UTtre7AHZqb |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 633f241:
|
sy-records
left a comment
There was a problem hiding this comment.
Can you add a test for this?
There was a problem hiding this comment.
@sy-records
As we all know, this func getAndRemoveConfig has been used for much places.
It seems we need separate it for different functions in case of unpredicted issues.
WDTY?
sy-records
commented
Jun 24, 2021
Yes, you're right. |
trusktr
commented
Jun 24, 2021
@Koooooo-7 What do you mean? |
Koooooo-7
commented
Jun 25, 2021
This func r working in multi place to get configs. such as titles , sidebar headings. |
trusktr
commented
Jun 25, 2021
@Koooooo-7 I see what you're saying, although it seems very unlikely. My guess would be that there is no one relying on he non-working double quotes. It seems multiple people have hit this issue, and we closed the issues. It was in fact working before, then it broke: |
luwol03
commented
Jun 25, 2021
sure, will try that.
I dont think so. I would also like to use the double ones inside of headlines, or other stuff. Everywhere I can use this style. And another question, do you prefere an clean commit history, so should I rebase merge upstream changes? |
@luwol03 of cuz we can support this feat for those configs. instead, how about those titles/other stuff without configs but with " ? |
luwol03
commented
Jun 25, 2021
Then we should improve the function, so that it only replaces the quotes, if they are followed by a |
agreed. |
luwol03
commented
Jun 25, 2021
Is this normal, that your e2e tests failed? |
Koooooo-7
commented
Jun 25, 2021
It seems not this changes broken, it's okay. |
@Koooooo-7 can you point them out for us? ESIT: Oh NVM, i see you checked already and think it is fine. |
trusktr
commented
Jun 25, 2021
Sometimes it fails for some reason despite that it shouldn't. Needs a fix. |
luwol03
commented
Jun 25, 2021
Before merge, I will try that:
|
Is anyone using it without the |
Here is an example without the colon: #1587 (comment)
|
| str: `[filename](_media/example.md ":include")`, | ||
| }); | ||
| }); | ||
| }); |
There was a problem hiding this comment.
I wonder what the behavior should actually be. Seems funky that it leaves things behind. Seems like it should handle everything.
trusktr
commented
Jun 25, 2021
@jhildenbiddle One test or other keeps randomly failing. |
trusktr
commented
Jun 25, 2021
Investigating the failures. Let's not merge until we know it isn't the change from here. Seems unlikely that it is. |
trusktr
left a comment
There was a problem hiding this comment.
Looks good. I'm not requesting any changes, just blocking from merging to ensure the test is just flaky (that's what it seems like).
trusktr
commented
Jun 25, 2021
I re-ran the test like 6 times already, and one (at random) still keeps failing. |
trusktr
commented
Jun 25, 2021
I don't think we should do that, it could break this: Thanks @luwol03! Merging, since tests pass except one at random, which seems unrelated. |
Oh, A few seconds ago, I pushed my changes, before I relized, that you already merged this changes 😂 Can you please take a look at my new commit? @trusktr Should I open a new PR for that? |
sy-records
commented
Jun 27, 2021
@luwol03 You can open a new PR |
luwol03
commented
Jun 28, 2021
|
Summary
I fixed a bug where
":include"is not handled like':include'. This is not working because the type of quotes are not supported. The default prettier configuration changes the''to"". And if you have auto format toggled on, you're not be able to save the file with the right quotes.What kind of change does this PR introduce?
I added added the
"also the the replace regexFor any code change,
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
Related issue, if any:
closes#1597
closes#1587
closes#1555
closes#1005
Tested in the following browsers: