Using plugin config callback about aurelia-kendoui-bridge

[charlespockert]

Sounds good, we could provide some defaults for all widgets that are in the core framework and another for all those in the pro framework to make it easier for people that just wanted access to everything

[JeroenVinke]

👍 good one

@adriatic can you setup the organizational structure in github so that we can assign people to issues if needed? I also wonder who needs to agree with changes like this before we can start working on it

[adriatic]

On setup the organizational structure issue:

It's all in place actually - just not enabled.

[charlespockert]

FYI, I thought this was a no brainer so I've added it in this commit

c63949a

It expects a list of control names - e.g. ['button', 'grid', 'autocomplete'] etc.

I'll leave this open for now as I want to add sensible defaults (e.g. core/pro defaults etc)

The reason we need this anyway is that Aurelia attempts to load any resources that are globalized. This means it will throw an error on startup if it can't find the Kendo files for a particular plugin.

[charlespockert]

Also thinking it would be nice if the user could configure in a more strongly typed way, e.g.

.plugin('aurelia-kendo', (plugins) => {     plugins.kendoGrid();
plugins.kendoButton():
});

Etc

[adriatic]

On this comment

I'll leave this open for now as I want to add sensible defaults (e.g. core/pro defaults etc)

I think that the same rules that apply to Aurelia config callback apply here as well: having an "empty use" statement like

aurelia.use

may not default to the usual:

aurelia.use
      .standardConfiguration()
      .developmentLogging()
      });

In any way, choosing a good default is the expected courtesy to the users

[JeroenVinke]

@charlespockert already made an awesome plugin callback here 😄