refactor: add usecase layer for param operations#4
Closed
mpyw wants to merge 2 commits intorefactor/usecase-layerfrom
Closed
refactor: add usecase layer for param operations#4mpyw wants to merge 2 commits intorefactor/usecase-layerfrom
mpyw wants to merge 2 commits intorefactor/usecase-layerfrom
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## refactor/usecase-layer #4 +/- ##
==========================================================
+ Coverage 89.66% 90.08% +0.41%
==========================================================
Files 65 71 +6
Lines 4393 4579 +186
==========================================================
+ Hits 3939 4125 +186
Misses 304 304
Partials 150 150
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Add usecase layer for SSM Parameter Store operations that returns structured data instead of formatting output. New usecases: - ShowUseCase: returns ShowOutput with parameter metadata - ListUseCase: returns ListOutput with entries (optionally with values) - LogUseCase: returns LogOutput with version history - DiffUseCase: returns DiffOutput with comparison data - SetUseCase: creates/updates parameters with tagging support - DeleteUseCase: deletes parameters This is Step 3 of the usecase layer architecture refactoring plan. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add tests for all param usecase operations with 100% coverage: - delete_test.go: DeleteUseCase tests - diff_test.go: DiffUseCase tests with version/shift support - list_test.go: ListUseCase tests with filters and pagination - log_test.go: LogUseCase tests with date filters - set_test.go: SetUseCase tests with tagging operations - show_test.go: ShowUseCase tests with version/shift support Key mock patterns: - Use fresh slice copies for GetParameterHistory to avoid in-place mutation issues with slices.Reverse - Support sequential GetParameter calls for multi-spec operations - Proper AWS SDK v2 variadic options signatures 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
mpyw
force-pushed
the
refactor/usecase-param
branch
from
f7bc029 to
ab39f03
Compare
3 tasks
Owner
Author
|
Superseded by #8 |
This was referenced Jan 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
internal/usecase/param/package with structured input/output typesThis is Step 3 of the usecase layer architecture refactoring plan.
Test plan
🤖 Generated with Claude Code