Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for version ranges #4583

Merged
merged 10 commits into from
Aug 12, 2019
Prev Previous commit
Document ranged versions
  • Loading branch information
Elchi3 committed Aug 8, 2019
commit f879c9fe118bec4818541d9aa7c87b606f390e47
11 changes: 11 additions & 0 deletions schemas/compat-data-schema.md
Original file line number Diff line number Diff line change
Expand Up @@ -226,6 +226,17 @@ Examples:
}
```

### Ranged versions

For certain browsers, ranged versions are allowed as it is sometimes impossible to find out in which early version of a browser a feature shipped. The statement below means "supported in at least version 37 and probably in earlier versions as well".
Currently, the only allowed ranged version is `"≤37"` for `webview_android`. There will be more ranged versions for other browsers in the future but ranged versions aren't generally allowed for every version string. Ranged versions should be used sparingly and only when it is impossible to find out the version number a feature initially shipped in.
ddbeck marked this conversation as resolved.
Show resolved Hide resolved

```json
{
"version_added": "≤37",
}
```

#### `prefix`
A prefix to add to the sub-feature name (defaults to empty string).
If applicable, leading and trailing `-` must be included.
Expand Down