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.

Sign up for GitHub

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

Jump to bottom

Add support for version ranges #4583

Merged
merged 10 commits into from
Aug 12, 2019
Merged

Add support for version ranges #4583

merged 10 commits into from
Aug 12, 2019

Commits on Aug 8, 2019

  1. feat(versions): Add basic support for version ranges

    @ExE-Boss @Elchi3
    ExE-Boss authored and Elchi3 committed Aug 8, 2019
    Configuration menu
    Copy the full SHA
    10bb9d7 View commit details
    Browse the repository at this point in the history

  2. fix(scripts): Mark version ranges as true values in stats script (E… 

    …B-Forks#2)

* Mark version ranges as `true` values in stats script

Co-Authored-By: Vinyl Darkscratch <vinyldarkscratch@gmail.com>

* refactor(scripts): Format `statistics.js`

Co-Authored-By: ExE Boss <3889017+ExE-Boss@users.noreply.github.com>
    @queengooborg @ExE-Boss @Elchi3
    2 people authored and Elchi3 committed Aug 8, 2019
    Configuration menu
    Copy the full SHA
    8e8cb9c View commit details
    Browse the repository at this point in the history

  3. docs: Improve version range documentation wording 

    Co-Authored-By: Vinyl Darkscratch <vinyldarkscratch@gmail.com>
    @ExE-Boss @queengooborg @Elchi3
    2 people authored and Elchi3 committed Aug 8, 2019
    Configuration menu
    Copy the full SHA
    39b55ab View commit details
    Browse the repository at this point in the history

  4. test(versions): Restrict <= to WebView 37

    @ExE-Boss @Elchi3
    ExE-Boss authored and Elchi3 committed Aug 8, 2019
    Configuration menu
    Copy the full SHA
    0b50386 View commit details
    Browse the repository at this point in the history

  5. fix(versions): Separate true and range values in statistics

    @ExE-Boss @Elchi3
    ExE-Boss authored and Elchi3 committed Aug 8, 2019
    Configuration menu
    Copy the full SHA
    e75852e View commit details
    Browse the repository at this point in the history

  6. feat(versions): Use ≤ as the version range prefix 

      I personally don’t like this, as it’s very hard to type.
    @ExE-Boss @Elchi3
    ExE-Boss authored and Elchi3 committed Aug 8, 2019
    Configuration menu
    Copy the full SHA
    f155338 View commit details
    Browse the repository at this point in the history

  7. fix(versions) Rename RANGE_PREFIX_LT to RANGE_PREFIX_LTE

    @ExE-Boss @Elchi3
    ExE-Boss authored and Elchi3 committed Aug 8, 2019
    Configuration menu
    Copy the full SHA
    4fc2ed8 View commit details
    Browse the repository at this point in the history

  8. Don't export RANGE_PREFIX_LTE

    @Elchi3
    Elchi3 committed Aug 8, 2019
    Configuration menu
    Copy the full SHA
    88b0d5b View commit details
    Browse the repository at this point in the history

  9. range -> ranged values in output table

    @Elchi3
    Elchi3 committed Aug 8, 2019
    Configuration menu
    Copy the full SHA
    5f2f3f2 View commit details
    Browse the repository at this point in the history

  10. Document ranged versions

    @Elchi3
    Elchi3 committed Aug 8, 2019
    Configuration menu
    Copy the full SHA
    f879c9f View commit details
    Browse the repository at this point in the history