markburns / markburns/interactify
contract validation in long chains
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Contract validation across a chain like the following does not spot the promise in Promiser and raises an error about Expecter needing it.
`organize` -> `Promiser`, (`If` -> chain(`Expecter`))
```ruby
organize \
Promiser.promising(:thing),
self.if(
:condition,
then: ExpectingThing = chain
'ChainedThings',
Expecter
),
else: SomethingElse
)
```
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
Start by reproducing the chained organizer example from the issue and trace the contract-validation path that reports Expecter as missing a promise. Done means validation recognizes the promise supplied by Promiser in the long chain and no longer raises that error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100