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.

Sign up for GitHub

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

Jump to bottom

Split read and write operations into different modules #58

Open
Pfeil opened this issue Oct 4, 2022 · 0 comments
Open

Split read and write operations into different modules #58

Pfeil opened this issue Oct 4, 2022 · 0 comments
Labels
long-term May take a while to resolve, e.g., solution is a steady task (scout rule). maintenance Not a bug, but should be done.

Comments

@Pfeil
Copy link
Member

Pfeil commented Oct 4, 2022

Sonarlint detected too many responsibilities in HandleProtocolAdapter.java (#57 (comment)).

  • I was considering splitting the resolving of PIDs and write-operations like create or update anyway in order to be able to resolve PIDs from (potentially) multiple systems in case this feature will be required at some point.
  • Also, the conversion of record representations could be externalized.
@Pfeil Pfeil added the maintenance Not a bug, but should be done. label Oct 4, 2022
@Pfeil Pfeil mentioned this issue Oct 5, 2022
Open
4 tasks
@Pfeil Pfeil added the long-term May take a while to resolve, e.g., solution is a steady task (scout rule). label Nov 15, 2023
@Pfeil Pfeil changed the title Evaluate architecture regarding having classes with too many responsibilities. Split read and write operations into different modules Aug 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
long-term May take a while to resolve, e.g., solution is a steady task (scout rule). maintenance Not a bug, but should be done.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Pfeil