notion / rxjoin

Rx observable plumbing for the JVM

RxJoin

Rx observable plumbing for the JVM

rxjoin's Issues

Add validation for each process step.

Things that immediately come to mind:

• @Out annotated element must be field or method, must be or return Observable
• @In annotated element must extend Subject
• @Plumbed annotated element must be a Type, must be public
• @Out and @In elements with the same value must be parameterized by the same type
• @Out elements must have unique annotation values (e.g. only one element can be annotated with @Out("color") in the example app)

All of these are fatal conditions, which require a descriptive message to be displayed to the user.

Create binding classes via factory

As more binding classes are added to the mapper, initialization will become more costly. Let's create them via factory instead.

Integrate with Travis.

https://travis-ci.org/

Validate In-annotated items' types

Example:

Given @Out("foo") Observable<Integer> is declared in a given @Joined class, anything Subject annotated with @In("foo") must be parameterized with Integer.

Change API entry point or lib name.

The names of the library and API entry point should correlate. Either change the name of the lib to Plumbing, or change the name of the API entry point to Plumb.