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

Refactor FileManager class to be non-static #2708

Closed
tenthe opened this issue Apr 7, 2024 · 0 comments · Fixed by #2709
Closed

Refactor FileManager class to be non-static #2708

tenthe opened this issue Apr 7, 2024 · 0 comments · Fixed by #2709
Labels
refactoring Indicates when a pull request or issue contains larger refactoring aspects.
Milestone

Comments

@tenthe
Copy link
Contributor

tenthe commented Apr 7, 2024

Body

The FileManager class is currently implemented as static, which makes it difficult to test and maintain. Refactoring it to be non-static will improve code organization and testability.

StreamPipes Committer

I acknowledge that I am a maintainer/committer of the Apache StreamPipes project.

@tenthe tenthe linked a pull request Apr 7, 2024 that will close this issue
@bossenti bossenti added this to the 0.95.0 milestone Apr 8, 2024
@bossenti bossenti added the refactoring Indicates when a pull request or issue contains larger refactoring aspects. label Apr 8, 2024
tenthe added a commit that referenced this issue Apr 8, 2024
* refactor(#2708): Make all methods of FileManager none static

* refactor(#2708): Add unit tests for getAllFiles

* refactor(#2708): Add unit tests for getFile

* refactor(#2708): Add tests in FileManager for storeFile and deleteFile

* refactor(#2708): Make FileHasher none static and add tests

* refactor(#2708): Add unit test for checkFileContentChanged in FileManager

* refactor(#2708): Remove hash code from FileMetadata
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Indicates when a pull request or issue contains larger refactoring aspects.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants