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

No strict bloop check in build #772

Merged
merged 3 commits into from
Mar 11, 2022
Merged

No strict bloop check in build #772

merged 3 commits into from
Mar 11, 2022

Commits on Mar 10, 2022

  1. Tweak --strict-bloop-json-check option 

    When --strict-bloop-json-check=false was passed, it seems we were not
updating Bloop files when new sources we added (or former ones removed).
This should fix that.
    @alexarchambault
    alexarchambault committed Mar 10, 2022
    Configuration menu
    Copy the full SHA
    07724ac View commit details
    Browse the repository at this point in the history

  2. Temporarily disable --strict-bloop-json-check=false in build 

    This option should speed up compilation, by short-circuiting costly
Bloop file generation when the build is apparently the same. As of now,
this option doesn't overwrite the Bloop files when new sources are
created, which is a problem.
    @alexarchambault
    alexarchambault committed Mar 10, 2022
    Configuration menu
    Copy the full SHA
    95fb465 View commit details
    Browse the repository at this point in the history

  3. Sort files when reading them from directories just in case

    @alexarchambault
    alexarchambault committed Mar 10, 2022
    Configuration menu
    Copy the full SHA
    e3f7e1d View commit details
    Browse the repository at this point in the history