> + @Override
> + public PagedIterable<T> apply(ListPage<T> input) {
> + if (input.nextMarker() == null)
> + return PagedIterables.of(input);
> +
> + Optional<Object> project =
> tryFind(request.getCaller().get().getArgs(), instanceOf(String.class));
> +
> + Optional<Object> zone = tryFind(request.getCaller().get().getArgs(),
> instanceOf(String.class));
> +
> + Optional<Object> listOptions =
> tryFind(request.getInvocation().getArgs(), instanceOf(ListOptions.class));
> +
> + assert project.isPresent() : String.format("programming error, method
> %s should have a string param for the "
> + + "project", request.getCaller().get().getInvokable());
> +
> + assert zone.isPresent() : String.format("programming error, method %s
> should have a string param for the "
> + + "zone", request.getCaller().get().getInvokable());
Any reason for `assert` here over `checkState`?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/16/files#r5362832
