Static attrs caching

[schwers-zz]

As mentioned in #1216, the static caching machinery introduced a regression; attrs were not considered during the isStatic calculation.

Note however that this assumes attrs will be static at component instantiation. Is dynamically changing the value of component.attrs supported? If so I think we'll need to add a setter and dynamically recompute isStatic

[mxstbr-bot]

	Warnings
⚠️	There are library changes, but not tests. That's OK as long as you're refactoring existing code

	Messages
📖	✅ Jest tests passed

Generated by 🚫 dangerJS

[mxstbr]

Thanks, shipping this!

[mxstbr]

Is dynamically changing the value of component.attrs supported?

I don't know why you'd do that, we'll see if people complain I guess!

[kitten]

@mxstbr wouldn’t that only be possible if the object is kept around and mutated or if the internals are being accessed? 😅

Definitely not supported, but possible I guess

[mxstbr]

Possible for sure, but that's what I mean—let's wait and see if anybody actually complains, then think about fixing it 😅

[vpicone]

@mxstbr I think one reason would be to integrate with 3rd party css libraries. For instance, PaperCSS has a popover property. You might want to change that dynamically. There might be a smarter way of doing that, just a thought.