You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are a lot of justfiles on github, and it would be nice to leverage them to make sure that existing justfiles aren't broken by future changes tojust.
I'm imagining a tool that would, for a new version of just:
download all files on named justfile or Justfile
check that all files are tokenized identically under the new and old versions
check that all files are parsed identically under the new and old versions
check that all files produce identical dry-runs under new and old versions
Caldera would be an appropriate name. It will probably need a blacklist for those files which are called justfile but which aren't actually justfiles.
The text was updated successfully, but these errors were encountered:
It will probably need a blacklist for those files which are called justfile but which aren't actually justfiles.
On the lower layer, it should be sufficient to generate a report for given version of just, some just-version. If it fails to parse today, it shouldn't be a problem tomorrow.
A higher layer would have to track tuples of (something-that-looks-like-justfile, just-version, report), and only raise red flags when there's a regression - something that worked with just-version is now broken in just-version+1.
Then there's no need for a hardcoded list - both whitelists and blacklists suck.
There are a lot of justfiles on github, and it would be nice to leverage them to make sure that existing justfiles aren't broken by future changes to
just
.I'm imagining a tool that would, for a new version of just:
justfile
orJustfile
Caldera would be an appropriate name. It will probably need a blacklist for those files which are called
justfile
but which aren't actually justfiles.The text was updated successfully, but these errors were encountered: