Categories: None [Edit]
interactor-contracts
Interactors are a pattern for structuring your business logic into units.
They have a flexible context that they pass between them, which makes them
easy-to-write, but hard-to-understand after you've written them. Much of
this confusion comes from not knowing what the interactor is supposed to
take as input and what it's expected to produce.
Enter contracts. Contracts allow you define, up front, a contract both for
the input of an interactor, known as expectations, and the output of it,
known as promises. Additionally, you can define a handler for what happens
when an interactor violates its contracts, known as a breach.
Declaring these contracts can help define your interface and make it easier
to understand how to use an interactor. They form both documentation and
validation for your business logic.
Total
Ranking: 6,248 of 183,139
Downloads: 662,518
Daily
Ranking: 5,922 of 183,127
Downloads: 181
Downloads Trends
Ranking Trends
Num of Versions Trends
Popular Versions (Major)
Popular Versions (Major.Minor)
Depended by
Rank | Downloads | Name |
---|---|---|
48,364 | 21,076 | cron_to_go_sync |
117,461 | 5,267 | prelands_rails |
130,996 | 4,270 | interactify |
Depends on
Rank | Downloads | Name |
---|---|---|
1 | 2,410,461,295 | bundler |
628 | 68,402,240 | dry-validation |
1,510 | 18,823,820 | interactor |
Owners
# | Gravatar | Handle |
---|---|---|
1 | michaeljherold |