6header.usePage("幻灯片");
7header.useFunctions([], "hide");
8
9function startCreateSlides() {10 window.zhihui.slides.openCreateSlideWindow();
11 console.log("create");
12}
14 });
15}
16
17export async function exportSlides(18 dir: string,
19 options: {
20 dark?: boolean;
7 });
8}
9
10export async function buildSlides(dir: string, npx: string) {11 const script = `${npx} slidev build --download`;
12 execSync(script, {
13 cwd: dir,
1import { exec as $, execSync } from "node:child_process";
2
3export async function createServer(dir: string, npx: string) { 4 const script = `${npx} slidev`;
5 return $(script, {
6 cwd: dir,
18 return json["dist-tags"].latest;
19}
20
21export async function createProject(22 dist: string,
23 projectName: string,
24 theme: string,
It is recommended to have documentation comments above, or right inside a function/class declaration. This helps developers, users and even the author understand the purpose of a code snippet or API function in the future.
NOTE: If you want to stop this issue from getting raised on certain constructs (arrow functions, class expressions, methods etc.), consider using the skipdoccoverage option under the analyzers.meta
property in your .deepsource.toml
file.
For example, the following configuration will silence this issue for class expressions and method definitions:
[analyzers.meta]
skip_doc_coverage = ["class-expression", "method-definition"]
function sum(a, b) {
return a + b;
}
/**
* Function to add two numbers
* @param a The first number to add
* @param b The second number to add
* @returns The sum of two numbers
*/
function sum(a, b) {
return a + b;
}