History

DOCS/compatibility.rst: add requirement when changing default values

Documented default values are relied upon by scripts, so changing these values can casuse incompatible changes. This makes documenting them required.

nanahi committed 2 years ago

Commit 46dbaff1 parent eb38c3c1 file · +7 −0Browse files

Unified · Split

DOCS/compatibility.rst+7−0
@@ -29,6 +29,13 @@ All of these are important for interfacing both with end users and API users · 28 unmodified lines
29(which include Lua scripts, libmpv, and the JSON IPC). As such, they constitute29(which include Lua scripts, libmpv, and the JSON IPC). As such, they constitute
30a large part of the user interface and APIs.30a large part of the user interface and APIs.
31 31
32Certain options and commands may have documented default values. These default
33values are considered a part of the API since scripts may already rely on these
34documented behaviors. Changing these defaults are considered incompatible
35changes and must be documented. Undocumented default values do not subject to
36this requirement, and it is recommended to discourage such usage in the related
37documentations if there is a need to frequently change such defaults.
38
32All incompatible changes to this must be declared in interface-changes.rst,39All incompatible changes to this must be declared in interface-changes.rst,
33which include the types of changes, the impact of these changes, and suggested40which include the types of changes, the impact of these changes, and suggested
34actions to address such impact so that the incompatibility is alleviated.41actions to address such impact so that the incompatibility is alleviated.

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t