There is currently no way to view the raw fingerprint data, only the SHA (they'd like to be able to list the backpack react stuff just like you would with get library targets #33
The content of a fingerprint is actually not meant to be human-readable. It's interesting to see how many fingerprints are on a Commit. But after that, the fingerprint is actually not-displayable. We could add the context of optional "summary" data and that's kind of interesting. It could be nicely formatted readable representations of what the fingerprint has captured. But in general, fingerprints are not code snippets. They can represent a "quality" of code that is represented by text in different files (ie a function, an import, a package dep, and a config entry)!
The content of a fingerprint is actually not meant to be human-readable. It's interesting to see how many fingerprints are on a Commit. But after that, the fingerprint is actually not-displayable. We could add the context of optional "summary" data and that's kind of interesting. It could be nicely formatted readable representations of what the fingerprint has captured. But in general, fingerprints are not code snippets. They can represent a "quality" of code that is represented by text in different files (ie a function, an import, a package dep, and a config entry)!