Skip to content
This repository was archived by the owner on Apr 4, 2023. It is now read-only.
This repository was archived by the owner on Apr 4, 2023. It is now read-only.

Feature: orchestration of method chains #1

@onyxrev

Description

@onyxrev

Currently you can orchestrate the top-level call with default scenarios underneath:

API::FakeAccountsClient::V2.class_call(:oauth_access_tokens).yields(:success)

API::FakeAccountsClient::V2.oauth_access_tokens.create
success!

But that would also make the following succeed:

API::FakeAccountsClient::V2.class_call(:oauth_access_tokens).yields(:success)

API::FakeAccountsClient::V2.oauth_access_tokens.destroy
success!

... which may not provide sufficiently fine-grained control.

I'd like to be able to do something like:

API::FakeAccountsClient::V2.class_call(:oauth_access_tokens, :create).yields(:success)

Or maybe even:

API::FakeAccountsClient::V2.class_call(:oauth_access_tokens, :create).yields(:success, :failure)

You get the idea. The syntax is up for discussion.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions