Skip to content

Commit 75448e2

Browse files
authored
describe having the two new attributes missing
per notepad-plus-plus/nppPluginList#424 (comment), there are still some plugins that have neither of those attributes, so I needed to remove a statement that claimed that those attributes were required, and instead highly encourage checking historical compatibility before submitting an entry that was missing those attributes.
1 parent 852aeba commit 75448e2

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

content/docs/plugins.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -346,8 +346,7 @@ and the rest should be intuitive.
346346
if _maximum_ is empty, it will mean that the plugin will work with any version of
347347
Notepad++ after (and including) the _minimum_; you cannot set both empty.
348348
The version numbers will be dotted versions, such as `8.0`, `8.2`, `8.3.1` . If you
349-
have spaces anywhere between the `[]` brackets, it will not work. If the attribute
350-
is not in your plugin's entry in the JSON, it will not work.
349+
have spaces anywhere between the `[]` brackets, it will not work.
351350
352351
example | meaning
353352
---|---
@@ -385,6 +384,11 @@ and the rest should be intuitive.
385384
Similar to npp-compatible-versions, you cannot have spaces inside or between the `[]`.
386385
You may leave out the _pluginminimum_ and/or _nppminimum_, as shown in the examples,
387386
but it likely doesn't make sense to leave out either of the maximums.
387+
388+
If both of those attributes are missing, it is interpreted that your plugin has no API calls
389+
that are incompatible with any version of Notepad++, and it will run with and not crash any
390+
version of Notepad++. Before submitting a plugin without those attributes, please be certain
391+
of the historical compatibility. Thank you.
388392
389393
### Do your PR to join plugin list
390394

0 commit comments

Comments
 (0)