Skip to content

Utlity naming for Event Sources #1098

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

Merged
merged 3 commits into from
Mar 29, 2022
Merged

Utlity naming for Event Sources #1098

merged 3 commits into from
Mar 29, 2022

Conversation

csviri
Copy link
Collaborator

@csviri csviri commented Mar 28, 2022

No description provided.

@csviri csviri self-assigned this Mar 28, 2022
@csviri
Copy link
Collaborator Author

csviri commented Mar 28, 2022

The failed tests seems to be a glitch because first I mistakenly pushed it to the main branch.

@jesperpedersen
Copy link

Wouldn't this be

Map<String, Collection<EventSource>>

instead ? Or are you assuming that you only have one EventSource per area ?

@csviri
Copy link
Collaborator Author

csviri commented Mar 28, 2022

Wouldn't this be

Map<String, Collection<EventSource>>

instead ? Or are you assuming that you only have one EventSource per area ?

It's basically a name of a single EventSource. To address it from different places.

@csviri csviri force-pushed the utlity-naming-es branch from 835310b to 9bedbca Compare March 29, 2022 07:29
@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

0.0% 0.0% Coverage
0.0% 0.0% Duplication

@csviri csviri merged commit 69e3f0c into main Mar 29, 2022
@csviri csviri deleted the utlity-naming-es branch March 29, 2022 07:43
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.

3 participants