Nathanael Silverman

@MetaSpl0day thanks for considering the license. It's pretty permissive and what you're describing sounds fine. Check out the "redistribution" part of the license here: https://github.com/airbnb/paris/blob/master/LICENSE#L89

Good point. We could still compute a view specific hashcode, and if it differs from that of the previously applied style before the view is drawn again the style could...

I'm wondering if Paris could assign a unique id to all the linked styles and use it to compare them. It would be more efficient than using equals like Epoxy...

@elihart reference equality wouldn't work for methods (or functions) annotated with `@Style`. The unique id could be a string signature of the field/method/property/function: ``` // field com.myapp.customviews.MyView#MY_STYLE // method com.myapp.customviews.MyView#myStyle()...

I'm concerned about styles with large drawables that we wouldn't want instantiated unless they're in use. 😔 Or just large styles in general.

For resources: ```kotlin @Style(MyView::class) val MY_STYLE_1 = R.style.MyStyle ``` (We could also use naming to automatically link styles.) For style builders couldn't the processor figure out the type of the...

@rene-dohan which custom styles attributes are you using? It's possible to add support for new attributes to Paris.

@rene-dohan support for external view types and attributes can be added using [View Proxies](https://github.com/airbnb/paris/wiki/View-Proxies). This can be done within the Paris project or within your own (if you're using Paris)....

@Zoha131 could you maybe create a pull request with your view proxy? I'd be happy to take a look and help debug.

@laurakelly style extension classes purposefully all use the same package so that they result in the same import statement regardless of which or how many views are being styled. However...