Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/husky #185

Merged
merged 6 commits into from
Mar 18, 2024
Merged

Feat/husky #185

merged 6 commits into from
Mar 18, 2024

Conversation

cre8
Copy link
Contributor

@cre8 cre8 commented Mar 18, 2024

Adding husky to work to format the files before commiting them.

Signed-off-by: Mirko Mollik [email protected]

Copy link

codecov bot commented Mar 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.02%. Comparing base (f19b76c) to head (ef9f151).
Report is 1 commits behind head on main.

❗ Current head ef9f151 differs from pull request most recent head 2ff575f. Consider uploading reports for the commit 2ff575f to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #185   +/-   ##
=======================================
  Coverage   98.02%   98.02%           
=======================================
  Files          23       23           
  Lines        2074     2074           
  Branches      307      307           
=======================================
  Hits         2033     2033           
  Misses         41       41           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@cre8
Copy link
Contributor Author

cre8 commented Mar 18, 2024

@lukasjhan When I am using the commit via the command line like git commit -m "fix: foo,....." it works fine. It seems that vscode git commit ui is ignoring the pre commit, so it will create two commits (which is not a big deal since all commits will be squashed).

I used husky because it had the biggest community

Copy link
Member

@lukasjhan lukasjhan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@berendsliedrecht
Copy link
Contributor

Not the biggest fan of husky as the CI validates everything and husky just slows me down :'). No real issue, just find it a bit annoying and thats mainly why we disabled it within Credo.

@lukasjhan
Copy link
Member

Not the biggest fan of husky as the CI validates everything and husky just slows me down :'). No real issue, just find it a bit annoying and thats mainly why we disabled it within Credo.

I've never used it before but, um.. Is it because husky check the codes every time I commit?

@cre8
Copy link
Contributor Author

cre8 commented Mar 18, 2024

@berendsliedrecht the problem with lerna publish is that it will update the package.json files to add the new version number, commit and push it. We can not stop in the middle to run the format command so it get's aligned with biome.

Or we go the other way around and change the biome rules so they fit with the changes lerna is performing.

@lukasjhan
Copy link
Member

I think it will be okay since the code base is not large like credo.

@berendsliedrecht
Copy link
Contributor

Yeah the size and biome performance should help a lot. As long as we don't have to wait for 50s+ for a commit it's all good :).

@cre8 cre8 merged commit 9356aee into openwallet-foundation-labs:main Mar 18, 2024
8 checks passed
@cre8 cre8 deleted the feat/husky branch March 18, 2024 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants