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

Enum refactoring 187998654 #401

Merged
merged 5 commits into from
Aug 1, 2024
Merged

Conversation

ernestoarbitrio
Copy link
Contributor

No description provided.

@ernestoarbitrio ernestoarbitrio requested a review from gergness July 24, 2024 08:41
Copy link

codecov bot commented Jul 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (56d03c5) to head (2599849).

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #401   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           20        20           
  Lines         4750      4756    +6     
=========================================
+ Hits          4750      4756    +6     

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

Copy link
Contributor

@gergness gergness left a comment

Choose a reason for hiding this comment

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

I don't have strong opinions on this, but not sure why moving the NUMERIC_CUBE_MEASURES out of enums is helpful? To me it feels like the natural place to define collections of measures is in cr.cube.enums, even if some of them are only used in one place.

I lose track of which enum conventions support what, but could it be a property of CUBE_MEASURES or does that only work when we don't subclass enum.Enum?

Again, I don't have strong opinions, so feel free to overrule.

@ernestoarbitrio
Copy link
Contributor Author

I don't have strong opinions on this, but not sure why moving the NUMERIC_CUBE_MEASURES out of enums is helpful? To me it feels like the natural place to define collections of measures is in cr.cube.enums, even if some of them are only used in one place.

I lose track of which enum conventions support what, but could it be a property of CUBE_MEASURES or does that only work when we don't subclass enum.Enum?

Again, I don't have strong opinions, so feel free to overrule.

agreed done! Thanks

@ernestoarbitrio ernestoarbitrio merged commit 12c68b2 into master Aug 1, 2024
8 checks passed
@ernestoarbitrio ernestoarbitrio deleted the enum-refactoring-187998654 branch August 1, 2024 08:39
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.

2 participants