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

[3.0] Consider making the storage/repository package internal (or merging into storage) #5492

Open
2 tasks done
dweymouth opened this issue Feb 3, 2025 · 0 comments
Open
2 tasks done
Labels
future Features that might take a while to be sheduled refactor Issues related to refactoring code.

Comments

@dweymouth
Copy link
Contributor

Checklist

  • I have searched the issue tracker for open issues that relate to the same feature, before opening a new one.
  • This issue only relates to a single feature. I will open new issues for any other features.

Is your feature request related to a problem?

Currently we have some duplicated public APIs between the storage and storage/repository packages. This isn't ideal, but is unavoidable with the current package layout.

Is it possible to construct a solution with the existing API?

No response

Describe the solution you'd like to see.

consider redesigning the package hierarchy to avoid duplicating public APIs

@Jacalz Jacalz added future Features that might take a while to be sheduled refactor Issues related to refactoring code. labels Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future Features that might take a while to be sheduled refactor Issues related to refactoring code.
Projects
None yet
Development

No branches or pull requests

2 participants