Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Include source context in preparation_logs #74
http://188.8.131.52/report/75a1bc73-8f68-4b3e-b751-8aea4172fc93 doesn't tell us where the source was in the
(I know the source is the CSV parser's URL, because I opened that page from that cell in the dashboard homepage table, but I can't tell this from the report page itself :)
I'll think of it! We have some more information stored to show about the source as well.
One report can have many sources, if the sources produce the same input for font bakery (by sha256 hash and environment version). We could remove that (possible) many-to-one relationship by creating more (potentially equal) reports though. I'm not sure anymore, if that hashing/environment version thing is a good idea to pursue though, also because of that thing (we talked about it before) that our font-bakery specification is not idempotent.