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

chore: Automatic UserMappingOptions methods implementation #41

Merged
merged 2 commits into from
Aug 22, 2024

Conversation

evanxg852000
Copy link
Contributor

@evanxg852000 evanxg852000 commented Aug 8, 2024

Ticket(s) Closed

What

Added a dependency on strum create to automatically provide as_ref & iter methods to enums. More can be added if needed.

Why

The strum can be used to remove useful manual implementations

How

Tests

Made sure the as_ref & iter methods provide the expected output.

@evanxg852000 evanxg852000 requested review from neilyio and removed request for philippemnoel August 8, 2024 17:38
@Weijun-H
Copy link
Contributor

Weijun-H commented Aug 9, 2024

I’m uncertain if adding new dependencies just to time this refactoring is justified.

@evanxg852000
Copy link
Contributor Author

@Weijun-H 👍🏾 Indeed this was also my concern given it's currently used in one place. However, I discussed this with a team member. It was deemed ok since it's lightweight. It would be perfectly valid if the consensus is to put this aside for now to avoid further dependencies. It's not a critical change anyway.

Copy link
Contributor

@rebasedming rebasedming left a comment

Choose a reason for hiding this comment

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

Nice! If we're going to refactor, let's apply this change everywhere.

@Weijun-H
Copy link
Contributor

Nice! If we're going to refactor, let's apply this change everywhere.

How about merging this PR first and then splitting the refactoring task into multiple "good first issue" tasks?

@philippemnoel
Copy link
Collaborator

Nice! If we're going to refactor, let's apply this change everywhere.

How about merging this PR first and then splitting the refactoring task into multiple "good first issue" tasks?

That sounds great. Could you please help open up the issues and link them in the PR here? Then we can merge the PR

@Weijun-H
Copy link
Contributor

Nice! If we're going to refactor, let's apply this change everywhere.

How about merging this PR first and then splitting the refactoring task into multiple "good first issue" tasks?

That sounds great. Could you please help open up the issues and link them in the PR here? Then we can merge the PR

file a ticket #80 to track

@rebasedming rebasedming force-pushed the strum-for-better-emums branch from 953d8b4 to 269172f Compare August 22, 2024 14:58
@rebasedming rebasedming merged commit 8e6fb4c into dev Aug 22, 2024
8 checks passed
@rebasedming rebasedming deleted the strum-for-better-emums branch August 22, 2024 15:41
shamb0 pushed a commit to shamb0/pg_analytics that referenced this pull request Aug 24, 2024
* added strum to automatically provide as_ref & iter methods to enums

* convert to strum

---------

Co-authored-by: Ming Ying <[email protected]>
shamb0 pushed a commit to shamb0/pg_analytics that referenced this pull request Aug 24, 2024
* added strum to automatically provide as_ref & iter methods to enums

* convert to strum

---------

Co-authored-by: Ming Ying <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants