Artifact e89c4d57a4a48b9333f963ef59d6d3c9d2f2a0cc3c38f8ae97128fb8dbe48fc5:

Wiki page [api] by mario on 2018-07-03 20:06:27.
D 2018-07-03T20:06:27.419
L api
N text/x-markdown
P 7ccf61855f0fa1a82970a92075b225027f533d0a812028da239fcadb636d8c1a
U mario
W 914
## # api:

An optional field to precise which application a script/plugin belongs to:

    # api: streamtuner2

Which is a vanity tag foremost. You wouldn't *normally* mix scripts from
different applications or languages and expect them to behave or work at all.

  * Nonetheless it makes sense for installation management, or filtering
    in plugin download repositories.

  * Additionally you still want to do some verification, such as

        $meta.api ~= /^(|myapi|altname|python)$/

  * Usually you'd allow `# api: language` for generic plugins (not bound to
    specific API).

  * And you might very well combine scripts from different APIs (in the same
    language, that is). For instance if one plugin implemented a stub API:

        # provide: api:archnemesis

  * Essentially `# api: NAME` is a shortcut for `# depends: api:NAME`.
    See also [depends](wiki/depends)



Z 36727f10beb4f4d710162a53d1b20b1a