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

Move event types into separate crate #559

Merged
merged 1 commit into from
Jan 25, 2024

Conversation

dfaust
Copy link
Member

@dfaust dfaust commented Jan 25, 2024

Move event types into separate crate.

Closes #487.

Copy link
Member

@0xpr03 0xpr03 left a comment

Choose a reason for hiding this comment

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

Looks good. Thanks for the work!

Let me know if you want this merged. I'm always unsure whether PRs are "WIP" / informative or actually "ready for merge" when they're opened without any flaws.

@dfaust
Copy link
Member Author

dfaust commented Jan 25, 2024

Please merge it.
I'll try to be clear in case I have a WIP PR.

@0xpr03 0xpr03 merged commit 08e74da into notify-rs:main Jan 25, 2024
13 checks passed
@0xpr03
Copy link
Member

0xpr03 commented Jan 25, 2024

I'll do a crate push / release once I'm back home today.

@0xpr03
Copy link
Member

0xpr03 commented Jan 25, 2024

I'll try to be clear in case I have a WIP PR.

Sounds good. I've just seen a lot of PRs where in the time it took me to actually review them, they got additional commits for fixups. So I would've prematurely merged stuff if I would've been faster. (Finding typos is something I always do afterwards..)

@dfaust
Copy link
Member Author

dfaust commented Jan 25, 2024

That's true. Happens to me all the time. And if I can, I fix those issues immediately. But if you merge my PR "too quick", it's still my fault for requesting bad code to be merged. So don't worry - and it can always be fixed later.

@dfaust
Copy link
Member Author

dfaust commented Jan 25, 2024

I'll do a crate push / release once I'm back home today.

Maybe hold back on that and check #560.

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.

Proposal: split Event structure into its own crate (notify-events?)
2 participants