npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

cloverx-doc

v1.3.5

Published

🍀convert cloverx api definition into swagger specific format

Downloads

15

Readme

cloverx-doc

🍀convert cloverx api definition into swagger specific format

Usage

Install

npm i cloverx-doc --save

The baseDir shoud have follow directory struct.

.
├── controller # Your api definitions must be created in this folder.
│   └── v1
│       ├── bundle.js
│       └── deep
│           └── client.js
└── schema
    └── swagger
        └── definitions.js # Your data model definations are here

then comment your api following jsdoc style

/**jsdoc
 * The description of your api
 * @tags client, cli
 * @httpMethod post
 * @path /bundle/:platform
 * @param {string#path} platform - description
 * @param {string#formData} dependencies - description, support markdown
 * ```javascirpt
 * Example
 * {
 *   "dfc": "~1.1.0"
 * }
 * ```
 * @response [@Module]
 */
function dependencies() {

}

and finally

const cloverxDoc = require('cloverx-doc');
let output = cloverxDoc.convert({
    baseDir: baseDir
    config: {
        host: '127.0.0.1:7078', // server address
        schemes: ['http'], // protocol, optional: https, http
        basePath: '/', // the prefix of url path
        // info about your app
        info: {
            version: '1.0.1',
            title: 'clover doc test',
            description: 'from test'
        }
    }
});

the swaggerDoc which generated by above code can be see here

Comment Style

The wraper must start with /**jsdoc

/**jsdoc
 * The description of your api write at start of the comment body.
 * markdown support
 * @tag ...
 * @tag ...
 */

Tag Defination

tags

which collection that api was belonged to.
the tags was defined in schema/swagger/tags.yaml.
Example: @tags client, cli

httpMethod

The action of http request which in lowercae.
Example: @httpMethod post

path

The path part of url, Fianl Path = basePath + directory path + path

param

@param {data type#location} params name - comment
Avaliable location see here.
Avaliable data type see here

response

The Modules are defined in schema/swagger/definitions.js.

Basic

Grammar | Description :--------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------- @ModuleName | ref a module directly [@ModuleName] | wrap module in an array. When check the response, the array.length can be one or more, but the elements which are in the array must have the same type. {:@ModuleName} | the module can contain have one or more element which is restricted to same type. {keyA:@ModuleName, keyB:@ModuleName} | Similar to {:@ModuleName}, append the restriction of key-name.

Mix

Grammar | Description :------------------------------------------|:----------- {:[@ModuleName]} | - {keyA:[@ModuleName], keyB:@ModuleName} | -

Output-Checker

Have the same grammar with response

Init

const checker = cloverxDoc.checker({
    definitionsPath: 'The path to definitions of swagger module'
});

checkAndFormat

// will get a new list of formated `Module` object
// if there is a mismtach data type in sourceObj, it should throw an error
let res = checker
            .module('[@Module...]')
            .checkAndFormat(sourceObj);

Reference