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 events from internal to pkg #4812

Merged
merged 3 commits into from
Oct 25, 2024
Merged

Move events from internal to pkg #4812

merged 3 commits into from
Oct 25, 2024

Conversation

rdimitrov
Copy link
Member

Summary

The following PR moves events from internal to pkg

Change Type

Mark the type of change your PR introduces:

  • Bug fix (resolves an issue without affecting existing features)
  • Feature (adds new functionality without breaking changes)
  • Breaking change (may impact existing functionalities or require documentation updates)
  • Documentation (updates or additions to documentation)
  • Refactoring or test improvements (no bug fixes or new functionality)

Testing

Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.

Review Checklist:

  • Reviewed my own code for quality and clarity.
  • Added comments to complex or tricky code sections.
  • Updated any affected documentation.
  • Included tests that validate the fix or feature.
  • Checked that related changes are merged.

@rdimitrov rdimitrov self-assigned this Oct 24, 2024
@rdimitrov rdimitrov requested a review from a team as a code owner October 24, 2024 09:37
@JAORMX
Copy link
Contributor

JAORMX commented Oct 24, 2024

IMO we should move constructors and interfaces to pkg. But not the whole implementation.

@evankanderson
Copy link
Member

Can we defer this until after #4784 ?

@rdimitrov
Copy link
Member Author

Can we defer this until after #4784 ?

Of course 👍 Do you have any idea how much time you'll need?

@evankanderson
Copy link
Member

evankanderson commented Oct 24, 2024 via email

@rdimitrov rdimitrov force-pushed the move-events branch 2 times, most recently from d48e527 to 84a6698 Compare October 24, 2024 15:10
@coveralls
Copy link

coveralls commented Oct 24, 2024

Pull Request Test Coverage Report for Build 11515474144

Details

  • 54 of 84 (64.29%) changed or added relevant lines in 27 files are covered.
  • 3 unchanged lines in 3 files lost coverage.
  • Overall coverage increased (+0.006%) to 52.936%

Changes Missing Coverage Covered Lines Changed/Added Lines %
internal/email/awsses/awsses.go 0 1 0.0%
internal/email/noop/noop.go 0 1 0.0%
internal/entities/handlers/handler.go 14 15 93.33%
internal/events/stubs/eventer.go 0 1 0.0%
internal/providers/github/installations/installations.go 0 1 0.0%
internal/providers/gitlab/manager/webhook_handlers_repos.go 0 1 0.0%
internal/reminder/reminder.go 0 1 0.0%
internal/engine/handler.go 1 3 33.33%
internal/service/service.go 0 2 0.0%
internal/providers/gitlab/manager/webhook_handlers_merge_requests.go 0 3 0.0%
Files with Coverage Reduction New Missed Lines %
internal/reconcilers/reconcilers.go 1 60.0%
internal/engine/handler.go 1 73.08%
internal/reminderprocessor/reminder_processor.go 1 0.0%
Totals Coverage Status
Change from base Build 11514176926: 0.006%
Covered Lines: 13298
Relevant Lines: 25121

💛 - Coveralls

Signed-off-by: Radoslav Dimitrov <[email protected]>
Copy link
Contributor

@jhrozek jhrozek left a comment

Choose a reason for hiding this comment

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

The newly exported interface looks minimal enough. I tried merging @evankanderson 's branch atop this one and while there were conflicts, they could be resolved quite easily (rename of events.Setup to eventer.New)

@rdimitrov rdimitrov merged commit 30decca into main Oct 25, 2024
25 checks passed
@rdimitrov rdimitrov deleted the move-events branch October 25, 2024 10:11
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.

5 participants