pluginapi:infojson
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| pluginapi:infojson [2023/06/07 17:12] – James Sentman | pluginapi:infojson [2023/06/07 17:35] (current) – [Required Fields:] James Sentman | ||
|---|---|---|---|
| Line 17: | Line 17: | ||
| >**tag** String - Every plugin must have a custom “tag” value. This is how the plugin will be referenced internally even if the name changes. This must be unique. Xtension reserves all strings starting with “xt.” you should create a short string that contains something that sets yours apart from others thaat might make a similar plugin. For example “zwave” is a bad tag for an interface, consider instead something like “james.zwave.lutron” or something more specific. Don’t get too flowery. There is no limit to the length of the tag, but it will be stored many times in the database potentially and used in indexing and other things. | >**tag** String - Every plugin must have a custom “tag” value. This is how the plugin will be referenced internally even if the name changes. This must be unique. Xtension reserves all strings starting with “xt.” you should create a short string that contains something that sets yours apart from others thaat might make a similar plugin. For example “zwave” is a bad tag for an interface, consider instead something like “james.zwave.lutron” or something more specific. Don’t get too flowery. There is no limit to the length of the tag, but it will be stored many times in the database potentially and used in indexing and other things. | ||
| - | “tag”: | + | “tag”: |
| Line 52: | Line 52: | ||
| - | NEXT: [[pluginapi: | + | NEXT: [[pluginapi: |
pluginapi/infojson.1686157920.txt.gz · Last modified: 2023/06/07 17:12 by James Sentman