Some way to pass args to loader.

[evant]

For example, on signin, you'd want to pass a username and password to Loader#restart()

[evant]

Option 1

A single generic type param.

public class MyLoader extends Loader<Arg, Result> {
  @Override
  protected void onStart(Arg arg, Receiver receiver) { ... }
}

Arg arg = ...;
myLoader.start(arg);

pros:

• Type safety

cons:

• Requires boilerplate, even when you don't need args (ex: myLoader.start(null):).
  • There can be an overload which passes null to onStart() but that behavior can be surprising if not expecting it.
• Only one arg allowed.

Option 2

A vararg Object param.

public class MyLoader extends Loader<Result> {
  @Override
  protected void onStart(Object[] args, Receiver receiver) { ... }
}

Arg arg = ...;
myLoader.start(arg);

pros:

• As many arguments as you want (ex: myLoader.start(arg1, arg2)).
• No extra boilerplate if you don't need args (ex: myLoader.start()).

cons:

• No type safety or argument length safety.

Option 3

A Bundle param.

```java
public class MyLoader extends Loader<Result> {
  @Override
  protected void onStart(Bundle args, Receiver receiver) { ... }
}

Arg arg = ...;
Bundle args = new Bundle();
args.putParcelable("arg", arg);
myLoader.start(args);

pros:

• No extra type boilerplate if you don't need args.
• Arguments are 'named'
• Familiar interface for passing args.

cons:

• Boilerplate for creating args to pass.
• Types limited to bundle types even though data never needs to be parceled.
• Limited type safety.

[ersin-ertan]

I'm liking option 1, some of my networking calls using retrofit use @Post , having a single @Body LoginUserobject holding the credentials, so this pattern is familiar.