HashLoad / HashLoad/boss

Where's the first hash in boss-lock.json come from?

Open
#121 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
626
Forks
103
Avg merge
7d 2h
Merged PRs (30d)
5

Description

I'm writing a little Wizard that outputs a directory that looks very similar to e.g. https://github.com/Embarcadero/P4D-Data-Sciences/ as it's based on that layout. The 'Wizard' is just doing Token replacement so the end-product is a new set of components. This is possible as the originals have extremely minimal changes when creating a variant component.

The boss-lock.json I'm looking at starts....

{
	"hash": "d41d8cd98f00b204e9800998ecf8427e",
	"updated": "2022-06-08T17:04:13.2794469-07:00",
	"installedModules": {

I know that everything after installedModules is constant but am worried that the hash may be a hash of the files in the folder(s) that contain the boss-lock.json. If this is true how do I calculate one?

If the hash won't break anything then I've got nothing to worry about of course...
What happens if I omit it? I assume it's only relevant if you've got boss installed.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names boss-lock.json and its hash and installedModules fields, but no source file or test. Start by locating the code that writes boss-lock.json, then determine whether the hash is required and how it is calculated. Done means documenting the hash's purpose, omission behavior, and any calculation steps.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.