-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Ensure code format #2138
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
Ensure code format #2138
Conversation
…private methods and properties to start to encapsulate Docsify Also some small tweaks: - move initGlobalAPI out of Docsify.js to start to encapsulate Docsify - move ajax to utils folder - fix some type definitions and improve content in some JSDoc comments - use concise class field syntax - consolidate duplicate docsify-ignore comment removal code This handles a task in [Simplify and modernize Docsify](#2104), as well as works towards [Encapsulating Docsify](#2135).
…rettier script for manually formatting the whole code base
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
All reactions
Sorry, something went wrong.
7ecb4be
to
3bef45b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Sorry, something went wrong.
All reactions
Koooooo-7
Successfully merging this pull request may close these issues.
None yet
Summary
We're using prettier, so ensure we check code format as part of the
lint
script. Also add aprettier
script for manually formatting the whole code base.The issue and pull request templates needed formatting, so I went ahead and made some updates at the same time. This PR is now using the updated PR template.
Related issue, if any:
Part of
Continues from PR
What kind of change does this PR introduce?
Build-related changes
Repo settings
For any code change,
Does this PR introduce a breaking change?
No
Tested in the following browsers: