Skip to content

FetchDistinctLabelsUsecase is not very understandable. Is it even possible that two labels on the same target are the same if the constraints are correctly set in the db? And if this is for filtering for showing it in the UI, I don’t think this use case should even exist here. In that case, the presentation layer should do the filtering and decide which label of which target to show or to show that this label is set on both address as utxo for example. But this is not something to have a separate usecase for I feel. #330

FetchDistinctLabelsUsecase is not very understandable. Is it even possible that two labels on the same target are the same if the constraints are correctly set in the db? And if this is for filtering for showing it in the UI, I don’t think this use case should even exist here. In that case, the presentation layer should do the filtering and decide which label of which target to show or to show that this label is set on both address as utxo for example. But this is not something to have a separate usecase for I feel.

FetchDistinctLabelsUsecase is not very understandable. Is it even possible that two labels on the same target are the same if the constraints are correctly set in the db? And if this is for filtering for showing it in the UI, I don’t think this use case should even exist here. In that case, the presentation layer should do the filtering and decide which label of which target to show or to show that this label is set on both address as utxo for example. But this is not something to have a separate usecase for I feel. #330

Workflow file for this run

name: Claude Code
on:
issue_comment:
types: [created]
pull_request_review_comment:
types: [created]
permissions:
id-token: write # needed for OIDC
contents: write # so it can write the repo
issues: write # so it can comment on issues
pull-requests: write # so it can comment on PRs
jobs:
claude:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
token: ${{ secrets.GITHUB_TOKEN }}
fetch-depth: 0 # Fetch full history for branch operations
persist-credentials: true # Keep credentials for subsequent git commands
- uses: anthropics/claude-code-action@v1
with:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
claude_args: "--model claude-opus-4-5-20251101"