Skip to content

Support binding types with unresolved interfaces #359

@jonpryor

Description

@jonpryor

Context:
#358 (comment)

Imagine the following:

public interface Fooable {
}
public class Foo implements Fooable {
}

Further imagine that Foo and Fooable are in separate foo.jar and fooable.jar files, and we attempt to bind only foo.jar.

Should this work?

Offhand, I can't think of any reason why it shouldn't be supportable.

Does this work? No. As a specific example, consider recyclerview-v7-28.0.0-beta01.aar: android.support.v7.widget.RecyclerView is a non-abstract type which implements the interface android.support.v4.view.ScrollingView, which cannot be resolved (as it's in a different .jar file). The RecyclerView type is not bound.

Metadata

Metadata

Assignees

No one assigned

    Labels

    generatorIssues binding a Java library (generator, class-parse, etc.)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions