marigold-dev / marigold-dev/tzsafe
list of ticket in `arg`
Nobody has claimed this yet.
- Dominant language
- LigoLANG
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Theoretically there can be things you can do with tickets which require sending multiple different tickets at the same time. This would require `args` and the ticket input to be a list.
I guess it's hard to say whether it actually matters, since we have no use case in mind for this functionality anyway... Probably the most common use cases won't need this, I guess...?
Of course, if the example requires multiple different _types_ of tickets, then we're out of luck anyway. :frowning_face:
_Originally posted by @tj825 in https://github.com/marigold-dev/multisig/pull/19#discussion_r1116179870_
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue discusses supporting lists of args and tickets but names no files, tests, or entry points. First clarify a concrete use case and whether multiple ticket types must be supported; done would require an agreed scope and acceptance criteria before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100