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

Switch to Google's uuid module #34

Merged
merged 2 commits into from
May 2, 2024

Conversation

mikelolasagasti
Copy link
Contributor

satori/uuid repo is dead and has different problems as shown in satori/go.uuid#84

Although a fork exists to continue satori/uuid, Google's module is simpler and already used as indirect dependency.

Copy link
Contributor

@ranakan19 ranakan19 left a comment

Choose a reason for hiding this comment

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

We compared uuid libraries from google and gofrs at one point and decided to go ahead with gofrs/uuid at that point. I'd try comparing the two libraries, and if not much difference then for the sake of consistency it'd be better to use gofrs here as well.

Copy link
Contributor

@alexeykazakov alexeykazakov left a comment

Choose a reason for hiding this comment

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

Thanks!

`satori/uuid` repo is dead and has different problems as shown in
satori/go.uuid#84

Although a fork exists to continue `satori/uuid`, Google's module is
simpler and already used as indirect dependency.

Signed-off-by: Mikel Olasagasti Uranga <[email protected]>
@mikelolasagasti
Copy link
Contributor Author

We compared uuid libraries from google and gofrs at one point and decided to go ahead with gofrs/uuid at that point. I'd try comparing the two libraries, and if not much difference then for the sake of consistency it'd be better to use gofrs here as well.

My goal was to reduce the amount of dependencies. gofrs or google's module perform similar, so one or another is not a big change, but Google's is used by 4x more projects than gofrs' module. I can change the PR if required.

What should change is also github.com/codeready-toolchain/toolchain-common to import either a newer gofrs (v3 vs v5) or move to Google's.

@ranakan19
Copy link
Contributor

We compared uuid libraries from google and gofrs at one point and decided to go ahead with gofrs/uuid at that point. I'd try comparing the two libraries, and if not much difference then for the sake of consistency it'd be better to use gofrs here as well.

My goal was to reduce the amount of dependencies. gofrs or google's module perform similar, so one or another is not a big change, but Google's is used by 4x more projects than gofrs' module. I can change the PR if required.

What should change is also github.com/codeready-toolchain/toolchain-common to import either a newer gofrs (v3 vs v5) or move to Google's.

Yep, here is the PR for upgrading the uuid to v5 - codeready-toolchain/toolchain-common#388

@alexeykazakov
Copy link
Contributor

Could you please resolve the conflict so we can get it merged?

Copy link

codecov bot commented May 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.57%. Comparing base (4e12832) to head (2597328).

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #34   +/-   ##
=======================================
  Coverage   65.57%   65.57%           
=======================================
  Files          41       41           
  Lines        2100     2100           
=======================================
  Hits         1377     1377           
  Misses        560      560           
  Partials      163      163           

@alexeykazakov alexeykazakov merged commit e9b5467 into kubesaw:master May 2, 2024
8 checks passed
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.

6 participants