You’re viewing Paradaux’s public workspaceSign in to vote and comment Get taskl.ie for your team

Paradaux
Issues
PAR-294

PAR-294

Search in paradaux, or jump to…

Actions

Change themeDark, light or system↵

Copy current URL

Navigation

Issues

Board

Projects

Deployments

Teams

↑ ↓ navigate↵ openEsc close

Loading issues

Built with taskl.ie

Issues Projects Search

You’re viewing Paradaux’s public workspaceSign in to vote and comment Get taskl.ie for your team

Paradaux
Issues
PAR-294

PAR-294

Search in paradaux, or jump to…

Actions

Change themeDark, light or system↵

Copy current URL

Navigation

Issues

Board

Projects

Deployments

Teams

↑ ↓ navigate↵ openEsc close

Loading issue

Loading issues

Built with taskl.ie

Issues Projects Search

Loading issue

PAR-294 · Move @Singleton command-parameter resolvers out of utils/… · Paradaux · taskl.ie

Workspace

Teams

PParadauxSign in

PAR-294

Move @Singleton command-parameter resolvers out of utils/ into commands/resolvers/

Consistency cleanup following the ChestShop util/service split (PAR-282). utils/resolvers/ held @Singleton framework ParameterResolver<T> implementations (FirmNameResolver, FirmPlayerResolver, OnlineFirmNameResolver) plus their command-parameter value records (FirmName, OnlineFirmName) — DI'd components + command types, not pure utils.

Fix: move the package utils/resolvers/ → commands/resolvers/ (they resolve command parameters). Pure package move + import/FQN updates + redundant-import cleanup; behaviour unchanged.

Properties

Status: Pending release
Priority: Low
Assignee: Unassigned
Labels: Improvement
Project: Business
Milestone: No milestone

Details

Votes: 0 votes
Created: Jul 2

Sign in

Activity

tesks created the issue Jul 2
ParadauxIO linked a commit: Commit a5983b6 — Move @Singleton command-param resolvers out of utils/ into commands/resolvers/ (PAR-294) Jul 2
tesks set status to Pending Release Jul 2

Sign in to comment

Join the conversation, react to comments and vote on this issue.