> + */
> +package org.apache.jclouds.profitbricks.rest.binder.snapshot;
> +
> +import static com.google.common.base.Preconditions.checkNotNull;
> +import com.google.inject.Inject;
> +import java.util.HashMap;
> +import java.util.Map;
> +import
> org.apache.jclouds.profitbricks.rest.binder.BaseProfitBricksRequestBinder;
> +import org.apache.jclouds.profitbricks.rest.domain.Snapshot;
> +import org.jclouds.http.HttpRequest;
> +import org.jclouds.json.Json;
> +
> +public class UpdateSnapshotRequestBinder extends
> BaseProfitBricksRequestBinder<Snapshot.Request.UpdatePayload> {
> +
> + final Map<String, Object> requestBuilder;
> + final Json jsonBinder;
What about this comment? Something that makes sense for a separate PR? Also
I've noticed some binders declare the variables in the default scope. If there
is no good reason for that, they should be made private. We could address both
in a new PR.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/244/files#r55286102
