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

Linter: enforce that we use return value of check_exp #588

Merged
merged 4 commits into from
Jun 13, 2023
Merged

Linter: enforce that we use return value of check_exp #588

merged 4 commits into from
Jun 13, 2023

Commits on Jun 13, 2023

  1. Linter: enforce that we use return value of check_exp 

    If we don't use the return value of these functions, it results in a
nasty and hard to find bug. The linter should be able to offer some
protection, despite not being the perfect tool for the job.
    @hugomg
    hugomg committed Jun 13, 2023
    Configuration menu
    Copy the full SHA
    c2f805b View commit details
    Browse the repository at this point in the history

  2. Linter: run other checks even if Luacheck fails

    @hugomg
    hugomg committed Jun 13, 2023
    Configuration menu
    Copy the full SHA
    8ac5f37 View commit details
    Browse the repository at this point in the history

  3. Nothing much

    @hugomg
    hugomg committed Jun 13, 2023
    Configuration menu
    Copy the full SHA
    20d4fa7 View commit details
    Browse the repository at this point in the history

  4. Detect more cases of tabs mixed with spaces 

    Thankfully hasn't happened yet
    @hugomg
    hugomg committed Jun 13, 2023
    Configuration menu
    Copy the full SHA
    cd71262 View commit details
    Browse the repository at this point in the history