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

Add @Out(Void.class) annotations to writer implementations #119

Merged
merged 1 commit into from
Jul 22, 2013

Conversation

fsteeg
Copy link
Member

@fsteeg fsteeg commented Jul 19, 2013

The IDE uses the @In and @Out annotations to validate workflows. It issues warnings when no annotation is found. Since the writers don't actually output anything as part of the workflow, Void.class might make sense as their output type.

The IDE uses the `@In` and `@Out` annotations to validate workflows.
It issues warnings when no annotation is found. Since the writers
don't actually output anything as part of the workflow, `Void.class`
might make sense as their output type.
@cboehme cboehme merged commit f4c9e35 into metafacture:master Jul 22, 2013
@cboehme
Copy link
Member

cboehme commented Jul 22, 2013

Thanks for adding these. The idea of adding a something to mark a sink crossed my mind last week as well.

blackwinter added a commit that referenced this pull request Dec 13, 2024
Previously, when a wildcard matched multiple fields of which at least one was an array, `Hash.get()` returned a nested array (e.g., `[[Mary, University], Max]`).

Now, matched arrays are flattened (i.e., `[Mary, University, Max]`).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants