-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
trusktr testing (IGNORE THIS) #1414
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
Conversation
... need to test marked either, as we assume that the marked library works as advertised in whichever way they tested it.
This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
🔍 Inspect: https://vercel.com/docsify-core/docsify-preview/b949nbmh9
✅ Preview: https://docsify-preview-git-trusktr-testing.docsify-core.vercel.app
|
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 9847f69:
|
@trusktr FWIW, I don't think we need to test marked either. I only converted these tests from the old setup because I didn't want anyone to say "what happened to test X". I figured discussions about what tests we can get rid of could happen after the conversion.
Cool. Just testing anyway. The test didn't pass because importing marked directly does not include our custom additions.
Uh oh!
There was an error while loading. Please reload this page.
Just a PR I'm using for running tests.