Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Interface Type Instead of Concrete Class For Local Resource Properties #163

Open
sgarfinkel opened this issue May 6, 2020 · 0 comments
Assignees

Comments

@sgarfinkel
Copy link

Suppose Foo has a LocalResource property of type Bar, the following interface is generated:

public interface IBar {
...
}

public interface IFoo {
    void setBar(Bar bar);
    Bar getBar();
}

Instead, Lyo should use the generated interface IBar to properly decouple contracts and implementations.

@sgarfinkel sgarfinkel changed the title Use Interface Type Instead of Concrete Implementation For Local Resource Properties. Use Interface Type Instead of Concrete Class For Local Resource Properties May 6, 2020
@jadelkhoury jadelkhoury self-assigned this May 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants