super-grid is going to have a whole lot of features. One of the goals of this project is for outside collaborators to easily contribute. I don't know how readable Polymer element code usually is. Very OO oriented in a very fashionably functional world!
I propose we divide most of the feature sets (except core etc.) into Polymer Behaviors. By doing this, we will make it very easy for internal and external collaborators to isolate a problem based on the feature and add new features.
Eg: super-grid can have a different behavior for each of:
Row Selection.
Custom Renderers.
Custom Editors.
There would be the super-grid.html core element inherting all of these behaviors to finally create a grid that would have all of the above 3 features.
If there is a bug (or someone wants to add features) in say, the row selection. They would simply navigate to row-selection.html inside say a /behaviors and make a PR!
super-gridis going to have a whole lot of features. One of the goals of this project is for outside collaborators to easily contribute. I don't know how readable Polymer element code usually is. Very OO oriented in a very fashionably functional world!I propose we divide most of the feature sets (except core etc.) into Polymer Behaviors. By doing this, we will make it very easy for internal and external collaborators to isolate a problem based on the feature and add new features.
Eg:
super-gridcan have a different behavior for each of:There would be the
super-grid.htmlcore element inherting all of these behaviors to finally create a grid that would have all of the above 3 features.If there is a bug (or someone wants to add features) in say, the row selection. They would simply navigate to
row-selection.htmlinside say a/behaviorsand make a PR!