Opened at 2017-03-18T16:52:14Z
Last modified at 2022-10-02T19:43:42Z
#1095 new todo
handle command argument arity mismatch
| Reported by: | Ichthyostega | Owned by: | |
|---|---|---|---|
| Priority: | lesser | Milestone: | 1alpha |
| Component: | lumieraSteam | Keywords: | data interfaces sanity QA |
| Sub Tickets: | #1088 | Parent Tickets: | #55, #301, #1092, #1094 |
Description
When a command is bound to a concrete list of arguments, the right number of arguments is verified rather indirectly, raising a runtime type mismatch. Generally speaking, it can not be avoided to perform this check late, at runtime, simply because the precise command signature is erased before a command definition is stored into the registry. But it would be better to insert an explicit arity check way earlier in the invocation stack, for example in CommandImpl::setArguments() and to produce a clear error message at that point right away. Moreover, this is also the location where a branch for the more elaborate feature #1094 would be inserted, if we choose to implement such ever...
Change history (2)
comment:1 by , at 2022-10-02T19:43:42Z
| blocking: | 301, 55, 1092, 1094 → 55, 301, 1092, 1094 |
|---|---|
| Owner: | removed |
- Improvement of code-base quality.
- note that the design of Commands vs. Actions might significantly change the situation
comment:2 by , at 2025-12-25T00:00:00Z
| blockedby: | 1088 |
|---|---|
| blocking: | 55, 301, 1092, 1094 |
| Parent Tickets: | → 55, 301, 1092, 1094 |
| Sub Tickets: | → 1088 |
Migration MasterTickets ⟼ Subtickets-plugin
