Move namespace handler to service/frontend #3855
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Moved
namespace/handler.go
toservice/frontend/namespace_handler.go
.Renamed
namespace.ArchivalState
tonamespace.ArchivalConfigState
.Renamed
namespace.ArchivalEvent
tonamespace.ArchivalConfigEvent
.Why?
namespace
module is depending onarchiver
module, which will cause potential circular dependencies (eg:searchattribute
module cannot importnamespace
).Since the namespace handler is only used by
frontend
, I'm moving it there.As for the renaming, there's another type name
ArchivalState
already defined inarchiver
, so I'm changing the one in namespace to better distinguish them.How did you test it?
Existing tests.
Potential risks
No.
Is hotfix candidate?
No.