What if some grammar fails to update? Well, it gets removed from the
generated file. How would we know that the grammar failed? By reading
logs. Who reads logs if the command didn't crash? Right, nobody. Or even
if someone examines the logs, it is too easy to overlook the failure
(are you sure you read every single line of code? It is not even colored)
They are useful only in two cases:
- During debugging, this happens rarely
- Let's print something to keep the user informed that we are doing
something
It should not to be a mistake to overlook one line from the logs,
because when you run the same script hundreds of times (we do updates
weekly), you barely look at logs; you scan them, at most.
By treating logs this way, we can inform ourselves about possible
breakages before it gets even reviewed by another person, not by a user
opening a bug report months later.
Upstream no longer updating the sources in the lockfile.json, but they
still update in their main branch's parsers.lua. We don't need to parse
that file since nurr is already doing that for us. We can just grab
latest parser info from their json.
Heitor Augusto