fix: fix logical inconsistency in log entry formatting in index.html #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I noticed a logical inconsistency in the log entry formatting. The current code uses
padStart(5)
onnewBlock.hash
, which doesn't make sense for cryptographic hashes as they are typically much longer than 5 characters.To address this, I replaced
padStart(5)
withslice(0, 5)
to ensure only the first 5 characters of the hash are displayed. This change aligns with the intended behavior of showing a concise representation of the hash.This adjustment ensures the log entries are both meaningful and consistent.