Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define interceptors. #3

Closed
bigeasy opened this issue Jul 2, 2012 · 0 comments
Closed

Define interceptors. #3

bigeasy opened this issue Jul 2, 2012 · 0 comments
Assignees

Comments

@bigeasy
Copy link
Owner

bigeasy commented Jul 2, 2012

Like cleaup in Proof.

@ghost ghost assigned bigeasy Jul 2, 2012
bigeasy pushed a commit that referenced this issue Jul 3, 2012
While working with Proof, I keep considering ways to extend the control
flow features, but if it gets more complicated, it probably no longer
belongs in Proof.

I've made the root function a function that accepts a cadence, plus an
output callback. Currently, the output callback only handles errors,
there's now way to specify a return value for the entire cadence.

I've implemented an options hash that primes the context and accepts an
optional set of wrappers that will match a function name. This is how
Proof reintroduces its `cleanup` abilities, which have been removed from
the `invoke` method. See #3.

Created a `README.md`, with a short example. Will try to keep the
`README.md` updated as we go along.

Closes #6.
@bigeasy bigeasy closed this as completed in 38c41ac Jul 4, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant