| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/docsify-core/docsify-preview/kquxak60d |
Sorry, something went wrong.
…ments This reverts commit 90d283d
|
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 204bfbb:
|
Sorry, something went wrong.
There was a problem hiding this comment.
I think we should keep the <!-- {docsify-ignore} --> and also let the {docsify-ignore} work fine, in case of causing the second breaking for users who may already use the new option.
Sorry, something went wrong.
|
I agree with @Koooooo-7 if we can manage to to ship the changes it would be great. |
Sorry, something went wrong.
|
@anikethsaha @Koooooo-7 Done. In #1318, I had a reference to the need for compatibility. #1318 (review) |
Sorry, something went wrong.
There was a problem hiding this comment.
TODO: when and how we will solve it.
Sorry, something went wrong.
Awaiting @trusktr and @jhildenbiddle approval, release v4.11.6 |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM. For later, we can revert the PR merge commit to re-create these changes. We can open a PR with the changes, and just keep it open for v5 until we're ready.
Sorry, something went wrong.
|
Should we revert the removal of src from publish, then remove it as a breaking change for v5? Thoughts @jhildenbiddle? |
Sorry, something went wrong.
|
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks for doing this! This is good, to keep both forms.
Sorry, something went wrong.
There was a problem hiding this comment.
Oops. Looks good! Let's get this in.
Sorry, something went wrong.
|
@trusktr Do we have to wait for @jhildenbiddle ? Or can we merge and release patch versions now? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
<!-- {docsify-ignore} --> is a major change and should be put into v5.
But a version has already been released, so a patch version has been added that is compatible with older versions and can be removed in v5.
What kind of change does this PR introduce? (check at least one)
If changing the UI of default theme, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
You have tested in the following browsers: (Providing a detailed version will be better.)
If adding a new feature, the PR's description includes:
To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.