Reorganize the code to make the structure clearer. And also add an unit test for the internal ErofsCache.
Which issue(s) this PR fixes(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Please check the following list:
[x] Does the affected code have corresponding tests, e.g. unit test, E2E test?
[ ] Does this change require a documentation update?
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have an appropriate license header?
BigVan
commented
4 days ago
What this PR does / why we need it:
Reorganize the code to make the structure clearer. And also add an unit test for the internal ErofsCache.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged): Fixes #Please check the following list: